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 `str` literal, use double quotes
   |
LL |     "nope"
   |     ~~~~~~

error: aborting due to 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			`\|`
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			help: if you meant to write a `str` literal, use double quotes
			`\|`
			`LL \| "nope"`
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 19:07:19 -07:00			`\| ~~~~~~`
Move parse-fail tests to UI 2018-10-20 23:36:17 +03:00
Provide a span if main function is not present in crate Unfortunately, the diagnotic machinery does not cope well with an empty span which can happen if the crate is empty, in which case we merely set a spanless note. 2019-09-08 13:06:49 -04:00			`error: aborting due to previous error`
Move parse-fail tests to UI 2018-10-20 23:36:17 +03:00