rust/tests/ui/parser/use-unclosed-brace.stderr

error: this file contains an unclosed delimiter
  --> $DIR/use-unclosed-brace.rs:10:14
   |
LL | use foo::{bar, baz;
   |          - unclosed delimiter
...
LL | fn main() {}
   |             ^

error: aborting due to 1 previous error
Add unclosed brace in use tree test 2021-04-09 01:35:04 +00:00			`error: this file contains an unclosed delimiter`
Exit when there are unmatched delims to avoid noisy diagnostics 2023-02-28 07:55:19 +00:00			`--> $DIR/use-unclosed-brace.rs:10:14`
Add unclosed brace in use tree test 2021-04-09 01:35:04 +00:00			`\|`
			`LL \| use foo::{bar, baz;`
			`\| - unclosed delimiter`
			`...`
Avoid `;` -> `,` recovery and unclosed `}` recovery from being too verbose Those two recovery attempts have a very bad interaction that causes too unnecessary output. Add a simple gate to avoid interpreting a `;` as a `,` when there are unclosed braces. 2021-04-09 02:12:00 +00: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			`\| ^`
Add unclosed brace in use tree test 2021-04-09 01:35:04 +00: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`
Add unclosed brace in use tree test 2021-04-09 01:35:04 +00:00