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

struct Bug<A = [(); (let a = (), 1).1]> {
    //~^ ERROR expected expression, found `let` statement
    a: A
}

fn main() {}
Update issue-92893.stderr 2022-04-14 23:42:15 +03:00			`struct Bug<A = [(); (let a = (), 1).1]> {`
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 10:14:36 +00:00			//~^ ERROR expected expression, found `let` statement
Update issue-92893.stderr 2022-04-14 23:42:15 +03:00			`a: A`
			`}`

			`fn main() {}`