| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2023-09-13 | Address review comments | Matthew Jasper | -0/+2 | |
| - Add doc comment to new type - Restore "only supported directly in conditions of `if` and `while` expressions" note - Rename variant with clearer name | ||||
| 2023-09-11 | Reduce double errors for invalid let expressions | Matthew Jasper | -16/+6 | |
| Previously some invalid let expressions would result in both a feature error and a parsing error. Avoid this and ensure that we only emit the parsing error when this happens. | ||||
| 2023-09-11 | Move let expression checking to parsing | Matthew Jasper | -4/+2 | |
| There was an incomplete version of the check in parsing and a second version in AST validation. This meant that some, but not all, invalid uses were allowed inside macros/disabled cfgs. It also means that later passes have a hard time knowing when the let expression is in a valid location, sometimes causing ICEs. - Add a field to ExprKind::Let in AST/HIR to mark whether it's in a valid location. - Suppress later errors and MIR construction for invalid let expressions. | ||||
| 2023-01-11 | Move /src/test to /tests | Albert Larsan | -0/+1124 | |
