rust/tests/ui/parser/issues/issue-66473.stderr

error: unknown start of token: \u{348}
  --> $DIR/issue-66473.rs:1:2
   |
LL | #͈␀␀␀␀␀␀␀␀␀␀␀␀␀␀␀␀␀␀
   |  ^

error: unknown start of token: \u{0}
  --> $DIR/issue-66473.rs:1:3
   |
LL | #͈␀␀␀␀␀␀␀␀␀␀␀␀␀␀␀␀␀␀
   |  ^^^^^^^^^^^^^^^^^^
   |
   = help: source files must contain UTF-8 encoded text, unexpected null bytes might occur when a different encoding is used
   = note: character appears 17 more times

error: unknown start of token: \u{1d}
  --> $DIR/issue-66473.rs:4:2
   |
LL | ␋␝6␝␀␀
   |  ^

error: unknown start of token: \u{1d}
  --> $DIR/issue-66473.rs:4:4
   |
LL | ␋␝6␝␀␀
   |    ^

error: unknown start of token: \u{0}
  --> $DIR/issue-66473.rs:4:5
   |
LL | ␋␝6␝␀␀
   |     ^^
   |
   = help: source files must contain UTF-8 encoded text, unexpected null bytes might occur when a different encoding is used
   = note: character appears once more

error: expected one of `!` or `[`, found `6`
  --> $DIR/issue-66473.rs:4:3
   |
LL | #͈␀␀␀␀␀␀␀␀␀␀␀␀␀␀␀␀␀␀
   |  - expected one of `!` or `[`
...
LL | ␋␝6␝␀␀
   |   ^ unexpected token

error: aborting due to 6 previous errors
Add test for issue-66473 2020-01-15 08:34:51 +09:00			`error: unknown start of token: \u{348}`
compiletest: Require `//~` annotations even if `error-pattern` is specified 2025-03-29 02:41:32 +03:00			`--> $DIR/issue-66473.rs:1:2`
Add test for issue-66473 2020-01-15 08:34:51 +09:00			`\|`
Replace ASCII control chars with Unicode Control Pictures ``` error: bare CR not allowed in doc-comment --> $DIR/lex-bare-cr-string-literal-doc-comment.rs:3:32 \| LL \| /// doc comment with bare CR: '␍' \| ^ ``` 2024-07-09 16:46:09 +00:00			`LL \| #͈␀␀␀␀␀␀␀␀␀␀␀␀␀␀␀␀␀␀`
Add test for issue-66473 2020-01-15 08:34:51 +09:00			`\| ^`

			`error: unknown start of token: \u{0}`
compiletest: Require `//~` annotations even if `error-pattern` is specified 2025-03-29 02:41:32 +03:00			`--> $DIR/issue-66473.rs:1:3`
Add test for issue-66473 2020-01-15 08:34:51 +09:00			`\|`
Replace ASCII control chars with Unicode Control Pictures ``` error: bare CR not allowed in doc-comment --> $DIR/lex-bare-cr-string-literal-doc-comment.rs:3:32 \| LL \| /// doc comment with bare CR: '␍' \| ^ ``` 2024-07-09 16:46:09 +00:00			`LL \| #͈␀␀␀␀␀␀␀␀␀␀␀␀␀␀␀␀␀␀`
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 note about encoding when null bytes found 2021-02-06 19:17:14 -05:00			`\|`
Bless tests with new error wording 2021-02-07 11:11:38 -05:00			`= help: source files must contain UTF-8 encoded text, unexpected null bytes might occur when a different encoding is used`
Emit a single error for contiguous sequences of Unicode homoglyphs 2023-01-07 16:33:05 +00:00			`= note: character appears 17 more times`
Add test for issue-66473 2020-01-15 08:34:51 +09:00
			`error: unknown start of token: \u{1d}`
compiletest: Require `//~` annotations even if `error-pattern` is specified 2025-03-29 02:41:32 +03:00			`--> $DIR/issue-66473.rs:4:2`
Add test for issue-66473 2020-01-15 08:34:51 +09:00			`\|`
Replace ASCII control chars with Unicode Control Pictures ``` error: bare CR not allowed in doc-comment --> $DIR/lex-bare-cr-string-literal-doc-comment.rs:3:32 \| LL \| /// doc comment with bare CR: '␍' \| ^ ``` 2024-07-09 16:46:09 +00:00			`LL \| ␋␝6␝␀␀`
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 test for issue-66473 2020-01-15 08:34:51 +09:00
			`error: unknown start of token: \u{1d}`
compiletest: Require `//~` annotations even if `error-pattern` is specified 2025-03-29 02:41:32 +03:00			`--> $DIR/issue-66473.rs:4:4`
Add test for issue-66473 2020-01-15 08:34:51 +09:00			`\|`
Replace ASCII control chars with Unicode Control Pictures ``` error: bare CR not allowed in doc-comment --> $DIR/lex-bare-cr-string-literal-doc-comment.rs:3:32 \| LL \| /// doc comment with bare CR: '␍' \| ^ ``` 2024-07-09 16:46:09 +00:00			`LL \| ␋␝6␝␀␀`
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 test for issue-66473 2020-01-15 08:34:51 +09:00
			`error: unknown start of token: \u{0}`
compiletest: Require `//~` annotations even if `error-pattern` is specified 2025-03-29 02:41:32 +03:00			`--> $DIR/issue-66473.rs:4:5`
Add test for issue-66473 2020-01-15 08:34:51 +09:00			`\|`
Replace ASCII control chars with Unicode Control Pictures ``` error: bare CR not allowed in doc-comment --> $DIR/lex-bare-cr-string-literal-doc-comment.rs:3:32 \| LL \| /// doc comment with bare CR: '␍' \| ^ ``` 2024-07-09 16:46:09 +00:00			`LL \| ␋␝6␝␀␀`
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 note about encoding when null bytes found 2021-02-06 19:17:14 -05:00			`\|`
Bless tests with new error wording 2021-02-07 11:11:38 -05:00			`= help: source files must contain UTF-8 encoded text, unexpected null bytes might occur when a different encoding is used`
Emit a single error for contiguous sequences of Unicode homoglyphs 2023-01-07 16:33:05 +00:00			`= note: character appears once more`
Add test for issue-66473 2020-01-15 08:34:51 +09:00
unify/improve/simplify attribute parsing 2020-03-05 11:42:56 +01:00			error: expected one of `!` or `[`, found `6`
compiletest: Require `//~` annotations even if `error-pattern` is specified 2025-03-29 02:41:32 +03:00			`--> $DIR/issue-66473.rs:4:3`
Add test for issue-66473 2020-01-15 08:34:51 +09:00			`\|`
Replace ASCII control chars with Unicode Control Pictures ``` error: bare CR not allowed in doc-comment --> $DIR/lex-bare-cr-string-literal-doc-comment.rs:3:32 \| LL \| /// doc comment with bare CR: '␍' \| ^ ``` 2024-07-09 16:46:09 +00:00			`LL \| #͈␀␀␀␀␀␀␀␀␀␀␀␀␀␀␀␀␀␀`
unify/improve/simplify attribute parsing 2020-03-05 11:42:56 +01:00			\| - expected one of `!` or `[`
compiletest: Require `//~` annotations even if `error-pattern` is specified 2025-03-29 02:41:32 +03:00			`...`
Replace ASCII control chars with Unicode Control Pictures ``` error: bare CR not allowed in doc-comment --> $DIR/lex-bare-cr-string-literal-doc-comment.rs:3:32 \| LL \| /// doc comment with bare CR: '␍' \| ^ ``` 2024-07-09 16:46:09 +00:00			`LL \| ␋␝6␝␀␀`
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			`\| ^ unexpected token`
Add test for issue-66473 2020-01-15 08:34:51 +09:00
Emit a single error for contiguous sequences of Unicode homoglyphs 2023-01-07 16:33:05 +00:00			`error: aborting due to 6 previous errors`
Add test for issue-66473 2020-01-15 08:34:51 +09:00