mathieu/os-rust
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
os-rust/tests/ui/parser/utf16-be-without-bom.stderr

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

118 lines
4 KiB
Text
Raw Normal View History

Add tests for new UTF-16 behavior
2021-02-07 10:05:43 -05:00
error: unknown start of token: \u{0}
--> $DIR/utf16-be-without-bom.rs:4:1
|
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 | ␀f␀n␀ ␀m␀a␀i␀n␀(␀)␀ ␀{␀}␀
Add tests for new UTF-16 behavior
2021-02-07 10:05:43 -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
Add tests for new UTF-16 behavior
2021-02-07 10:05:43 -05:00
error: unknown start of token: \u{0}
--> $DIR/utf16-be-without-bom.rs:4:3
|
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 | ␀f␀n␀ ␀m␀a␀i␀n␀(␀)␀ ␀{␀}␀
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 tests for new UTF-16 behavior
2021-02-07 10:05:43 -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
Add tests for new UTF-16 behavior
2021-02-07 10:05:43 -05:00
error: unknown start of token: \u{0}
--> $DIR/utf16-be-without-bom.rs:4:5
|
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 | ␀f␀n␀ ␀m␀a␀i␀n␀(␀)␀ ␀{␀}␀
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 tests for new UTF-16 behavior
2021-02-07 10:05:43 -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
Add tests for new UTF-16 behavior
2021-02-07 10:05:43 -05:00
error: unknown start of token: \u{0}
--> $DIR/utf16-be-without-bom.rs:4:7
|
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 | ␀f␀n␀ ␀m␀a␀i␀n␀(␀)␀ ␀{␀}␀
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 tests for new UTF-16 behavior
2021-02-07 10:05:43 -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
Add tests for new UTF-16 behavior
2021-02-07 10:05:43 -05:00
error: unknown start of token: \u{0}
--> $DIR/utf16-be-without-bom.rs:4:9
|
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 | ␀f␀n␀ ␀m␀a␀i␀n␀(␀)␀ ␀{␀}␀
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 tests for new UTF-16 behavior
2021-02-07 10:05:43 -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
Add tests for new UTF-16 behavior
2021-02-07 10:05:43 -05:00
error: unknown start of token: \u{0}
--> $DIR/utf16-be-without-bom.rs:4:11
|
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 | ␀f␀n␀ ␀m␀a␀i␀n␀(␀)␀ ␀{␀}␀
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 tests for new UTF-16 behavior
2021-02-07 10:05:43 -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
Add tests for new UTF-16 behavior
2021-02-07 10:05:43 -05:00
error: unknown start of token: \u{0}
--> $DIR/utf16-be-without-bom.rs:4:13
|
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 | ␀f␀n␀ ␀m␀a␀i␀n␀(␀)␀ ␀{␀}␀
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 tests for new UTF-16 behavior
2021-02-07 10:05:43 -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
Add tests for new UTF-16 behavior
2021-02-07 10:05:43 -05:00
error: unknown start of token: \u{0}
--> $DIR/utf16-be-without-bom.rs:4:15
|
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 | ␀f␀n␀ ␀m␀a␀i␀n␀(␀)␀ ␀{␀}␀
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 tests for new UTF-16 behavior
2021-02-07 10:05:43 -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
Add tests for new UTF-16 behavior
2021-02-07 10:05:43 -05:00
error: unknown start of token: \u{0}
--> $DIR/utf16-be-without-bom.rs:4:17
|
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 | ␀f␀n␀ ␀m␀a␀i␀n␀(␀)␀ ␀{␀}␀
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 tests for new UTF-16 behavior
2021-02-07 10:05:43 -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
Add tests for new UTF-16 behavior
2021-02-07 10:05:43 -05:00
error: unknown start of token: \u{0}
--> $DIR/utf16-be-without-bom.rs:4:19
|
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 | ␀f␀n␀ ␀m␀a␀i␀n␀(␀)␀ ␀{␀}␀
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 tests for new UTF-16 behavior
2021-02-07 10:05:43 -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
Add tests for new UTF-16 behavior
2021-02-07 10:05:43 -05:00
error: unknown start of token: \u{0}
--> $DIR/utf16-be-without-bom.rs:4:21
|
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 | ␀f␀n␀ ␀m␀a␀i␀n␀(␀)␀ ␀{␀}␀
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 tests for new UTF-16 behavior
2021-02-07 10:05:43 -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
Add tests for new UTF-16 behavior
2021-02-07 10:05:43 -05:00
error: unknown start of token: \u{0}
--> $DIR/utf16-be-without-bom.rs:4:23
|
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 | ␀f␀n␀ ␀m␀a␀i␀n␀(␀)␀ ␀{␀}␀
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 tests for new UTF-16 behavior
2021-02-07 10:05:43 -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
Add tests for new UTF-16 behavior
2021-02-07 10:05:43 -05:00
error: unknown start of token: \u{0}
--> $DIR/utf16-be-without-bom.rs:4:25
|
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 | ␀f␀n␀ ␀m␀a␀i␀n␀(␀)␀ ␀{␀}␀
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 tests for new UTF-16 behavior
2021-02-07 10:05:43 -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
Add tests for new UTF-16 behavior
2021-02-07 10:05:43 -05:00
error: expected one of `!` or `::`, found `n`
--> $DIR/utf16-be-without-bom.rs:4:4
|
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 | ␀f␀n␀ ␀m␀a␀i␀n␀(␀)␀ ␀{␀}␀
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 `!` or `::`
Detect extra space in keyword for better hint
2023-07-03 23:54:49 +08:00
|
help: consider removing the space to spell keyword `fn`
|
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 | ␀fn␀ ␀m␀a␀i␀n␀(␀)␀ ␀{␀}␀
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 tests for new UTF-16 behavior
2021-02-07 10:05:43 -05:00
error: aborting due to 14 previous errors
Reference in a new issue Copy permalink