rust-lang/rust
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity
Files
51b51b51d7931da85280382a81c4dd80c73ca754
rust/tests/ui/parser/issues/issue-68730.stderr

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

50 lines
1.3 KiB
Plaintext
Raw Normal View History

Use `next_point` to avoid ICE
2020-02-02 02:39:53 +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-68730.rs:8:5
Use `next_point` to avoid ICE
2020-02-02 02:39:53 +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 | enum␀em␀˂˂
Use `next_point` to avoid ICE
2020-02-02 02:39:53 +09: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
Use `next_point` to avoid ICE
2020-02-02 02:39:53 +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-68730.rs:8:8
Use `next_point` to avoid ICE
2020-02-02 02:39:53 +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 | enum␀em␀˂˂
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
Use `next_point` to avoid ICE
2020-02-02 02:39:53 +09:00
error: unknown start of token: \u{2c2}
compiletest: Require `//~` annotations even if `error-pattern` is specified
2025-03-29 02:41:32 +03:00
--> $DIR/issue-68730.rs:8:9
Use `next_point` to avoid ICE
2020-02-02 02:39:53 +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 | enum␀em␀˂˂
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
| ^^
Use `next_point` to avoid ICE
2020-02-02 02:39:53 +09:00
|
Emit a single error for contiguous sequences of Unicode homoglyphs
2023-01-07 16:33:05 +00:00
= note: character appears once more
Use `next_point` to avoid ICE
2020-02-02 02:39:53 +09:00
help: Unicode character '˂' (Modifier Letter Left Arrowhead) looks like '<' (Less-Than Sign), but it is not
|
Show diff suggestion format on verbose replacement ``` error[E0610]: `{integer}` is a primitive type and therefore doesn't have fields --> $DIR/attempted-access-non-fatal.rs:7:15 | LL | let _ = 2.l; | ^ | help: if intended to be a floating point literal, consider adding a `0` after the period and a `f64` suffix | LL - let _ = 2.l; LL + let _ = 2.0f64; | ```
2024-07-09 22:30:26 +00:00
LL - enum␀em␀˂˂
LL + enum␀em␀<<
|
Use `next_point` to avoid ICE
2020-02-02 02:39:53 +09:00
error: unknown start of token: \u{2c2}
compiletest: Require `//~` annotations even if `error-pattern` is specified
2025-03-29 02:41:32 +03:00
--> $DIR/issue-68730.rs:8:10
Use `next_point` to avoid ICE
2020-02-02 02:39:53 +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 | enum␀em␀˂˂
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
| ^
Use `next_point` to avoid ICE
2020-02-02 02:39:53 +09:00
|
help: Unicode character '˂' (Modifier Letter Left Arrowhead) looks like '<' (Less-Than Sign), but it is not
|
Show diff suggestion format on verbose replacement ``` error[E0610]: `{integer}` is a primitive type and therefore doesn't have fields --> $DIR/attempted-access-non-fatal.rs:7:15 | LL | let _ = 2.l; | ^ | help: if intended to be a floating point literal, consider adding a `0` after the period and a `f64` suffix | LL - let _ = 2.l; LL + let _ = 2.0f64; | ```
2024-07-09 22:30:26 +00:00
LL - enum␀em␀˂˂
LL + enum␀em␀˂<
|
Use `next_point` to avoid ICE
2020-02-02 02:39:53 +09:00
unify/improve/simplify attribute parsing
2020-03-05 11:42:56 +01:00
error: expected one of `#`, `>`, `const`, identifier, or lifetime, found `<`
compiletest: Require `//~` annotations even if `error-pattern` is specified
2025-03-29 02:41:32 +03:00
--> $DIR/issue-68730.rs:8:10
Use `next_point` to avoid ICE
2020-02-02 02:39:53 +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 | enum␀em␀˂˂
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
| ^ expected one of `#`, `>`, `const`, identifier, or lifetime
Use `next_point` to avoid ICE
2020-02-02 02:39:53 +09:00
error: aborting due to 5 previous errors
Reference in New Issue Copy Permalink