rust/tests/ui/parser/raw/raw-byte-string-literals.stderr

error: bare CR not allowed in raw string
  --> $DIR/raw-byte-string-literals.rs:4:9
   |
LL |     br"a
";
   |         ^

error: non-ASCII character in raw byte string literal
  --> $DIR/raw-byte-string-literals.rs:5:8
   |
LL |     br"é";
   |        ^ must be ASCII

error: found invalid character; only `#` is allowed in raw string delimitation: ~
  --> $DIR/raw-byte-string-literals.rs:6:5
   |
LL |     br##~"a"~##;
   |     ^^^^^

error: aborting due to 3 previous errors
Don't suggest using \r in raw strings 2019-06-10 10:32:15 -05:00			`error: bare CR not allowed in raw string`
Prohibit bare CRs in raw byte strings 2019-05-13 13:21:44 -05:00			`--> $DIR/raw-byte-string-literals.rs:4:9`
			`\|`
			`LL \| br"a ";`
			`\| ^`

Make non-ASCII errors more consistent. There are three kinds of "byte" literals: byte literals, byte string literals, and raw byte string literals. None are allowed to have non-ASCII chars in them. Two `EscapeError` variants exist for when that constraint is violated. - `NonAsciiCharInByte`: used for byte literals and byte string literals. - `NonAsciiCharInByteString`: used for raw byte string literals. As a result, the messages for raw byte string literals use different wording, without good reason. Also, byte string literals are incorrectly described as "byte constants" in some error messages. This commit eliminates `NonAsciiCharInByteString` so the three cases are handled similarly, and described correctly. The `mode` is enough to distinguish them. Note: Some existing error messages mention "byte constants" and some mention "byte literals". I went with the latter here, because it's a more correct name, as used by the Reference. 2022-11-02 23:17:37 -05:00			`error: non-ASCII character in raw byte string literal`
Prohibit bare CRs in raw byte strings 2019-05-13 13:21:44 -05:00			`--> $DIR/raw-byte-string-literals.rs:5:8`
Move parse-fail tests to UI 2018-10-20 15:36:17 -05:00			`\|`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| br"é";`
Handle `Span`s for byte and raw strings and add more detail 2021-01-23 14:48:31 -06:00			`\| ^ must be ASCII`
Move parse-fail tests to UI 2018-10-20 15:36:17 -05:00
			error: found invalid character; only `#` is allowed in raw string delimitation: ~
Introduce rustc_lexer The idea here is to make a reusable library out of the existing rust-lexer, by separating out pure lexing and rustc-specific concerns, like spans, error reporting an interning. So, rustc_lexer operates directly on `&str`, produces simple tokens which are a pair of type-tag and a bit of original text, and does not report errors, instead storing them as flags on the token. 2019-05-06 03:53:40 -05:00			`--> $DIR/raw-byte-string-literals.rs:6:5`
Move parse-fail tests to UI 2018-10-20 15:36:17 -05:00			`\|`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| br##~"a"~##;`
Introduce rustc_lexer The idea here is to make a reusable library out of the existing rust-lexer, by separating out pure lexing and rustc-specific concerns, like spans, error reporting an interning. So, rustc_lexer operates directly on `&str`, produces simple tokens which are a pair of type-tag and a bit of original text, and does not report errors, instead storing them as flags on the token. 2019-05-06 03:53:40 -05:00			`\| ^^^^^`
Move parse-fail tests to UI 2018-10-20 15:36:17 -05:00
Prohibit bare CRs in raw byte strings 2019-05-13 13:21:44 -05:00			`error: aborting due to 3 previous errors`
Move parse-fail tests to UI 2018-10-20 15:36:17 -05:00