rust/tests/ui/mir/issue-92893.stderr

error: expected expression, found `let` statement
  --> $DIR/issue-92893.rs:1:22
   |
LL | struct Bug<A = [(); (let a = (), 1).1]> {
   |                      ^^^
   |
   = note: only supported directly in conditions of `if` and `while` expressions

error: aborting due to previous error
[rustc_parse] Forbid lets in certain places 2022-06-25 06:08:38 -05:00			error: expected expression, found `let` statement
			`--> $DIR/issue-92893.rs:1:22`
			`\|`
			`LL \| struct Bug<A = [(); (let a = (), 1).1]> {`
			`\| ^^^`
Address review comments - 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-13 10:00:31 -05:00			`\|`
			= note: only supported directly in conditions of `if` and `while` expressions
[rustc_parse] Forbid lets in certain places 2022-06-25 06:08:38 -05:00
Move let expression checking to parsing 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-09-08 05:14:36 -05:00			`error: aborting due to previous error`
Update issue-92893.stderr 2022-04-14 15:42:15 -05:00