rust/tests/ui/parser/mismatched-braces/missing-close-brace-in-struct.stderr

error: this file contains an unclosed delimiter
  --> $DIR/missing-close-brace-in-struct.rs:13:65
   |
LL | pub(crate) struct Bar<T> {
   |                          - unclosed delimiter
...
LL | fn main() {}
   |                                                                ^

error: aborting due to 1 previous error
tweak wording of mismatched delimiter errors 2020-01-03 08:40:15 -05:00			`error: this file contains an unclosed delimiter`
Recover gracefully from `struct ` parse errors 2020-08-13 21:15:36 -07:00			`--> $DIR/missing-close-brace-in-struct.rs:13:65`
Reduce ammount of errors given unclosed delimiter When in a file with a non-terminated item, catch the error and consume the block instead of trying to recover it more granularly in order to reduce the amount of unrelated errors that would be fixed after adding the missing closing brace. Also point out the possible location of the missing closing brace. 2019-10-25 18:30:02 -07:00			`\|`
			`LL \| pub(crate) struct Bar<T> {`
tweak wording of mismatched delimiter errors 2020-01-03 08:40:15 -05:00			`\| - unclosed delimiter`
Reduce ammount of errors given unclosed delimiter When in a file with a non-terminated item, catch the error and consume the block instead of trying to recover it more granularly in order to reduce the amount of unrelated errors that would be fixed after adding the missing closing brace. Also point out the possible location of the missing closing brace. 2019-10-25 18:30:02 -07:00			`...`
			`LL \| fn main() {}`
Be more accurate about calculating `display_col` from a `BytePos` No longer track "zero-width" chars in `SourceMap`, read directly from the line when calculating the `display_col` of a `BytePos`. Move `char_width` to `rustc_span` and use it from the emitter. This change allows the following to properly align in terminals (depending on the font, the replaced control codepoints are rendered as 1 or 2 width, on my terminal they are rendered as 1, on VSCode text they are rendered as 2): ``` error: this file contains an unclosed delimiter --> $DIR/issue-68629.rs:5:17 \| LL \| ␜␟ts␀![{i \| -- unclosed delimiter \| \| \| unclosed delimiter LL \| ␀␀ fn rݻoa>rݻm \| ^ ``` 2024-07-09 17:00:19 +00:00			`\| ^`
Reduce ammount of errors given unclosed delimiter When in a file with a non-terminated item, catch the error and consume the block instead of trying to recover it more granularly in order to reduce the amount of unrelated errors that would be fixed after adding the missing closing brace. Also point out the possible location of the missing closing brace. 2019-10-25 18:30:02 -07:00
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 15:44:16 +00:00			`error: aborting due to 1 previous error`
Reduce ammount of errors given unclosed delimiter When in a file with a non-terminated item, catch the error and consume the block instead of trying to recover it more granularly in order to reduce the amount of unrelated errors that would be fixed after adding the missing closing brace. Also point out the possible location of the missing closing brace. 2019-10-25 18:30:02 -07:00