mirror of
https://github.com/rust-lang/rust.git
synced 2025-02-10 05:53:10 +00:00
333388fd3c
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.
9 lines
203 B
Plaintext
9 lines
203 B
Plaintext
error: expected expression, found `let` statement
|
|
--> $DIR/issue-92893.rs:1:22
|
|
|
|
|
LL | struct Bug<A = [(); (let a = (), 1).1]> {
|
|
| ^^^
|
|
|
|
error: aborting due to previous error
|
|
|