| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2023-01-11 | Move /src/test to /tests | Albert Larsan | -11/+0 | |
| 2020-02-14 | Suggest a comma if a struct initializer field fails to parse | Aaron Hill | -2/+3 | |
| Currently, we emit a "try adding a comma" suggestion if a comma is missing in a struct definition. However, we emit no such suggestion if a comma is missing in a struct initializer. This commit adds a "try adding a comma" suggestion when we don't find a comma during the parsing of a struct initializer field. The change to `src/test/ui/parser/removed-syntax-with-1.stderr` isn't great, but I don't see a good way of avoiding it. | ||||
| 2019-11-06 | Remove "here" from "expected one of X here" | Esteban Küber | -1/+1 | |
| 2019-01-21 | Accept more invalid code that is close to correct fields | Esteban Küber | -9/+2 | |
| 2019-01-20 | Tweak field parse error recovery | Esteban Küber | -2/+2 | |
| 2019-01-20 | Recover from parse errors in struct literal fields | Esteban Küber | -1/+3 | |
| Attempt to recover from parse errors while parsing a struct's literal fields by skipping tokens until a comma or the closing brace is found. This allows errors in other fields to be reported. | ||||
| 2019-01-06 | tests: Do not use `-Z parse-only`, continue compilation to test recovery | Vadim Petrochenkov | -2/+9 | |
| 2018-12-25 | Remove licenses | Mark Rousskov | -1/+1 | |
| 2018-10-21 | Move parse-fail tests to UI | Vadim Petrochenkov | -0/+8 | |
