| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2019-11-07 | move unescape_error_reporting to lexer/ | Mazdak Farrokhzad | -215/+0 | |
| 2019-09-25 | Fix issue #64732 | Haoran Wang | -1/+7 | |
| Based on issue #64732, when creating a byte literal with single quotes, the suggestion message would indicate that you meant to write a `str` literal, but we actually meant to write a byte string literal. So I changed the unescape_error_reporting.rs to decide whether to print out "if you meant to write a `str` literal, use double quotes", or "if you meant to write a byte string literal, use double quotes". | ||||
| 2019-07-24 | Rollup merge of #62917 - estebank:trailing-slash, r=matklad | Mazdak Farrokhzad | -1/+1 | |
| Always emit trailing slash error Fix #62913. r? @petrochenkov | ||||
| 2019-07-23 | Always emit trailing slash error | Esteban Küber | -1/+1 | |
| 2019-07-21 | move unescape module to rustc_lexer | Aleksey Kladov | -2/+1 | |
| 2019-06-10 | Don't suggest using \r in raw strings | Igor Matuszewski | -0/+5 | |
| 2019-06-08 | Prohibit bare CRs in raw byte strings | Igor Matuszewski | -0/+5 | |
| 2019-05-02 | introduce unescape module | Aleksey Kladov | -0/+200 | |
| 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 | ||||
