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

error: character literal may only contain one codepoint
  --> $DIR/lex-bad-char-literals-2.rs:3:5
   |
LL |     'nope'
   |     ^^^^^^
   |
help: if you meant to write a string literal, use double quotes
   |
LL |     "nope"
   |     ~    ~

error: aborting due to 1 previous error
[WIP] Fix tests 2019-01-20 04:37:58 +09:00			`error: character literal may only contain one codepoint`
tests: Do not use `-Z parse-only`, continue compilation to test recovery 2019-01-06 18:33:05 +03:00			`--> $DIR/lex-bad-char-literals-2.rs:3:5`
Move parse-fail tests to UI 2018-10-20 23:36:17 +03:00			`\|`
Update tests 2019-03-09 15:03:44 +03:00			`LL \| 'nope'`
Move parse-fail tests to UI 2018-10-20 23:36:17 +03:00			`\| ^^^^^^`
Increase spacing for suggestions in diagnostics Make the spacing between the code snippet and verbose structured suggestions consistent with note and help messages. 2019-10-23 22:20:58 -07:00			`\|`
review comment: `str` -> string in messages 2024-03-13 23:52:04 +00:00			`help: if you meant to write a string literal, use double quotes`
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 11:48:25 +03:00			`\|`
			`LL \| "nope"`
Use shorter span for existing `'` -> `"` structured suggestion 2024-03-09 01:07:23 +00:00			`\| ~ ~`
Move parse-fail tests to UI 2018-10-20 23:36:17 +03:00
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 15:44:16 +00:00			`error: aborting due to 1 previous error`
Move parse-fail tests to UI 2018-10-20 23:36:17 +03:00