about summary refs log tree commit diff
path: root/src/test/parse-fail/bad-char-literals.rs
AgeCommit message (Collapse)AuthorLines
2018-10-21Move parse-fail tests to UIVadim Petrochenkov-31/+0
2018-02-01Improve char escaping in lexer messagesRyan Cumming-1/+1
Currently ', " and \ are escaped as \', \" and \\ respectively. This leads to confusing messages such as `error: unknown start of token: \\` when encountering a single backslash. Fix by emitting printable ASCII characters directly. This will still escape \r, \n, \t and Unicode characters. Fixes #47902
2016-03-30fix compile-fail and parse-fail tests by blindly opting back intoFelix S. Klock II-1/+1
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.
2015-04-18Return nonzero exit code if there are errors at a stop pointFlorian Hahn-0/+2
2015-02-16Move remaning compile-fail tests that are rejected by the parser to parse-failFlorian Hahn-0/+29