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
167 B
Plaintext
9 lines
167 B
Plaintext
error: expected expression, found `let` statement
|
|
--> $DIR/avoid-invalid-mir.rs:5:6
|
|
|
|
|
LL | !let y = 42;
|
|
| ^^^
|
|
|
|
error: aborting due to previous error
|
|
|