| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2023-12-19 | Plumb awaitness of for loops | Eric Holk | -3/+11 | |
| 2023-12-14 | Change expr_trailing_brace to an exhaustive match to force new expression ↵ | GearsDatapacks | -3/+32 | |
| kinds to specify whether they contain a brace Add inline const and other possible curly brace expressions to expr_trailing_brace Add tests for `}` before `else` in `let...else` error Change to explicit cases for expressions with optional values when being checked for trailing braces Add tests for more complex cases of `}` before `else` in `let..else` statement Move other possible `}` cases into separate arm and add FIXME for future reference | ||||
| 2023-10-27 | Add gen blocks to ast and do some broken ast lowering | Oli Scherer | -1/+1 | |
| 2023-09-11 | Move let expression checking to parsing | Matthew Jasper | -1/+1 | |
| 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-03-12 | Remove `box_syntax` from AST and use in tools | clubby789 | -1/+0 | |
| 2022-12-01 | Make inline const block `ExprWithBlock` | Gary Guo | -0/+1 | |
| 2022-11-17 | Box `ExprKind::{Closure,MethodCall}`, and `QSelf` in expressions, types, and ↵ | Nicholas Nethercote | -1/+3 | |
| patterns. | ||||
| 2021-08-30 | Handle let-else initializer edge case errors | Cameron Steffen | -0/+27 | |
| 2020-12-24 | use matches!() macro in more places | Matthias Krüger | -9/+9 | |
| 2020-08-30 | mv compiler to compiler/ | mark | -0/+25 | |
