rust/tests/ui/lexer/lex-bad-char-literals-4.rs

//
// This test needs to the last one appearing in this file as it kills the parser
static c: char =
    '●  //~ ERROR: unterminated character literal
;
Display better snippet for invalid char literal Given this code: fn main() { let _ = 'abcd'; } The compiler would give a message like: error: character literal may only contain one codepoint: '; let _ = 'abcd'; ^~ With this change, the message now displays: error: character literal may only contain one codepoint: 'abcd' let _ = 'abcd' ^~~~~~ Fixes #30033 2016-01-07 16:12:28 +00:00			`//`
			`// This test needs to the last one appearing in this file as it kills the parser`
testsuite: merge some lexer testcases Now that the lexer is more robust, these tests don't need to be in separate files. Yay! 2014-06-16 21:12:44 +00:00			`static c: char =`
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			`'● //~ ERROR: unterminated character literal`
Make most lexer errors non-fatal Most errors that arise in the lexer can be recovered from. This allows for more than one syntax error to be reported at a time. 2014-05-23 22:20:46 +00:00			`;`