rust/tests/ui/attributes/key-value-non-ascii.stderr

error: non-ASCII character in byte string literal
  --> $DIR/key-value-non-ascii.rs:3:19
   |
LL | #[rustc_dummy = b"ﬃ.rs"]
   |                   ^ must be ASCII
   |
help: if you meant to use the UTF-8 encoding of 'ﬃ', use \xHH escapes
   |
LL | #[rustc_dummy = b"/xEF/xAC/x83.rs"]
   |                   ~~~~~~~~~~~~

error: aborting due to previous error
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 byte string literal`
parser: Collect tokens for values in key-value attributes 2021-01-24 07:41:12 -06:00			`--> $DIR/key-value-non-ascii.rs:3:19`
			`\|`
			`LL \| #[rustc_dummy = b"ﬃ.rs"]`
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			`\| ^ must be ASCII`
Fix invalid suggestions for non-ASCII characters in byte constants 2021-07-31 07:37:01 -05:00			`\|`
			`help: if you meant to use the UTF-8 encoding of 'ﬃ', use \xHH escapes`
			`\|`
			`LL \| #[rustc_dummy = b"/xEF/xAC/x83.rs"]`
Modify structured suggestion output * On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span 2021-06-21 21:07:19 -05:00			`\| ~~~~~~~~~~~~`
parser: Collect tokens for values in key-value attributes 2021-01-24 07:41:12 -06:00
			`error: aborting due to previous error`