rust/src/test/ui/parser/lex-bad-char-literals-1.rs

// compile-flags: -Z parse-only -Z continue-parse-after-error
static c3: char =
    '\x1' //~ ERROR: numeric character escape is too short
;

static s: &'static str =
    "\x1" //~ ERROR: numeric character escape is too short
;

static c: char =
    '\●' //~ ERROR: unknown character escape
;

static s: &'static str =
    "\●" //~ ERROR: unknown character escape
;
fix compile-fail and parse-fail tests by blindly opting back into parser recovery (so that expected errors match up) I'm opting into parser recovery in all these cases out of expediency, not because the error messages you get with recovery enabled are actually all that usable in all cases listed. 2016-03-25 19:36:03 -05:00			`// compile-flags: -Z parse-only -Z continue-parse-after-error`
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 17:20:46 -05:00			`static c3: char =`
			`'\x1' //~ ERROR: numeric character escape is too short`
			`;`

			`static s: &'static str =`
			`"\x1" //~ ERROR: numeric character escape is too short`
			`;`

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 16:12:44 -05:00			`static c: char =`
			`'\●' //~ ERROR: unknown character escape`
			`;`

			`static s: &'static str =`
			`"\●" //~ ERROR: unknown character escape`
			`;`