rust/tests/ui/lexer/lex-bad-char-literals-1.stderr

error: numeric character escape is too short
  --> $DIR/lex-bad-char-literals-1.rs:2:6
   |
LL |     '\x1'
   |      ^^^

error: numeric character escape is too short
  --> $DIR/lex-bad-char-literals-1.rs:6:6
   |
LL |     "\x1"
   |      ^^^

error: unknown character escape: `\u{25cf}`
  --> $DIR/lex-bad-char-literals-1.rs:10:7
   |
LL |     '\●'
   |       ^ unknown character escape
   |
   = help: for more information, visit <https://doc.rust-lang.org/stable/reference/expressions/literal-expr.html>
help: if you meant to write a literal backslash (perhaps escaping in a regular expression), consider a raw string literal
   |
LL |     r"\●"
   |     ~~~~~

error: unknown character escape: `\u{25cf}`
  --> $DIR/lex-bad-char-literals-1.rs:14:7
   |
LL |     "\●"
   |       ^ unknown character escape
   |
   = help: for more information, visit <https://doc.rust-lang.org/stable/reference/expressions/literal-expr.html>
help: if you meant to write a literal backslash (perhaps escaping in a regular expression), consider a raw string literal
   |
LL |     r"\●"
   |     ~~~~~

error: aborting due to 4 previous errors
Move parse-fail tests to UI 2018-10-20 20:36:17 +00:00			`error: numeric character escape is too short`
Remove `-Z continue-parse-after-error` 2020-01-08 18:25:42 +00:00			`--> $DIR/lex-bad-char-literals-1.rs:2:6`
Move parse-fail tests to UI 2018-10-20 20:36:17 +00:00			`\|`
compiletest: make path normalization smarter 2019-03-13 04:47:36 +00:00			`LL \| '\x1'`
introduce unescape module Currently, we deal with escape sequences twice: once when we lex a string, and a second time when we unescape literals. This PR aims to remove this duplication, by introducing a new `unescape` mode as a single source of truth for character escaping rules 2019-04-25 08:48:25 +00:00			`\| ^^^`
Move parse-fail tests to UI 2018-10-20 20:36:17 +00:00
			`error: numeric character escape is too short`
Remove `-Z continue-parse-after-error` 2020-01-08 18:25:42 +00:00			`--> $DIR/lex-bad-char-literals-1.rs:6:6`
Move parse-fail tests to UI 2018-10-20 20:36:17 +00:00			`\|`
compiletest: make path normalization smarter 2019-03-13 04:47:36 +00:00			`LL \| "\x1"`
introduce unescape module Currently, we deal with escape sequences twice: once when we lex a string, and a second time when we unescape literals. This PR aims to remove this duplication, by introducing a new `unescape` mode as a single source of truth for character escaping rules 2019-04-25 08:48:25 +00:00			`\| ^^^`
Move parse-fail tests to UI 2018-10-20 20:36:17 +00:00
Handle `Span`s for byte and raw strings and add more detail 2021-01-23 20:48:31 +00:00			error: unknown character escape: `\u{25cf}`
Remove `-Z continue-parse-after-error` 2020-01-08 18:25:42 +00:00			`--> $DIR/lex-bad-char-literals-1.rs:10:7`
Move parse-fail tests to UI 2018-10-20 20:36:17 +00:00			`\|`
compiletest: make path normalization smarter 2019-03-13 04:47:36 +00:00			`LL \| '\●'`
Tweak incorrect escaped char diagnostic 2019-03-20 18:45:25 +00:00			`\| ^ unknown character escape`
Handle `Span`s for byte and raw strings and add more detail 2021-01-23 20:48:31 +00:00			`\|`
Update links to Rust Reference page on literals in diagnostic Instead of linking to the old Rust Reference site on static.rust-lang.org, link to the current website doc.rust-lang.org/stable/reference instead in diagnostic about incorrect literals. 2023-06-10 16:34:16 +00:00			`= help: for more information, visit <https://doc.rust-lang.org/stable/reference/expressions/literal-expr.html>`
suggest using raw string literals when invalid escapes appear i'd guess about 70% of "bad escape" cases occur when someone meant to use a raw string literal because they're passing it directly to Regex::new(). this emits an advisory (Applicability::MaybeIncorrect) help: suggestion to the user that they use an r"" string, on top of the normal notes about looking at the string literal documentation/spec. 2022-02-14 19:21:43 +00:00			`help: if you meant to write a literal backslash (perhaps escaping in a regular expression), consider a raw string literal`
			`\|`
			`LL \| r"\●"`
			`\| ~~~~~`
Move parse-fail tests to UI 2018-10-20 20:36:17 +00:00
Handle `Span`s for byte and raw strings and add more detail 2021-01-23 20:48:31 +00:00			error: unknown character escape: `\u{25cf}`
Remove `-Z continue-parse-after-error` 2020-01-08 18:25:42 +00:00			`--> $DIR/lex-bad-char-literals-1.rs:14:7`
Move parse-fail tests to UI 2018-10-20 20:36:17 +00:00			`\|`
compiletest: make path normalization smarter 2019-03-13 04:47:36 +00:00			`LL \| "\●"`
Tweak incorrect escaped char diagnostic 2019-03-20 18:45:25 +00:00			`\| ^ unknown character escape`
Handle `Span`s for byte and raw strings and add more detail 2021-01-23 20:48:31 +00:00			`\|`
Update links to Rust Reference page on literals in diagnostic Instead of linking to the old Rust Reference site on static.rust-lang.org, link to the current website doc.rust-lang.org/stable/reference instead in diagnostic about incorrect literals. 2023-06-10 16:34:16 +00:00			`= help: for more information, visit <https://doc.rust-lang.org/stable/reference/expressions/literal-expr.html>`
suggest using raw string literals when invalid escapes appear i'd guess about 70% of "bad escape" cases occur when someone meant to use a raw string literal because they're passing it directly to Regex::new(). this emits an advisory (Applicability::MaybeIncorrect) help: suggestion to the user that they use an r"" string, on top of the normal notes about looking at the string literal documentation/spec. 2022-02-14 19:21:43 +00:00			`help: if you meant to write a literal backslash (perhaps escaping in a regular expression), consider a raw string literal`
			`\|`
			`LL \| r"\●"`
			`\| ~~~~~`
Move parse-fail tests to UI 2018-10-20 20:36:17 +00:00
			`error: aborting due to 4 previous errors`