| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2018-03-11 | in which some labels and notes are upgraded to structured suggestions | Zack M. Davis | -22/+0 | |
| (Meanwhile, a couple of parse-fail tests are moved to UI tests so that the reader can see the new output, and an existing UI test is given a more evocative name.) | ||||
| 2017-03-25 | Improve wording and spans for unexpected token | Esteban Küber | -1/+1 | |
| * Point at where the token was expected instead of the last token successfuly parsed. * Only show `unexpected token` if the next char and the unexpected token don't have the same span. * Change some cfail and pfail tests to ui test. * Don't show all possible tokens in span label if they are more than 6. | ||||
| 2017-03-24 | Point at last valid token on failed `expect_one_of` | Esteban Küber | -1/+3 | |
| ```rust error: expected one of `.`, `;`, `?`, `}`, or an operator, found `)` --> $DIR/token-error-correct-3.rs:29:9 | 25 | foo() | - expected one of `.`, `;`, `?`, `}`, or an operator after this ... 29 | } else { | ^ unexpected token ``` | ||||
| 2016-03-07 | update error messages in parse-fail tests | Jorge Aparicio | -1/+1 | |
| 2016-02-15 | Some error recovery in the parser | Nick Cameron | -0/+2 | |
| 2015-10-28 | libsyntax: improve error message when a statement is prefixed with a match ↵ | Kevin Butler | -0/+18 | |
| keyword | ||||
