rust/tests/ui/mir/issue66339.rs

// compile-flags: -Z mir-opt-level=3
// build-pass

// This used to ICE in const-prop

fn foo() {
    let bar = |_| { };
    bar("a");
}

fn main() {
    foo();
}
Bump mir-opt-level from 2 to 3 in tests 2021-03-04 07:35:11 -06:00			`// compile-flags: -Z mir-opt-level=3`
const-prop: Restrict scalar pair propagation We now only propagate a scalar pair if the Rvalue is a tuple with two scalars. This for example avoids propagating a (u8, u8) value when Rvalue has type `((), u8, u8)` (see the regression test). While this is a correct thing to do, implementation is tricky and will be done later. Fixes #66971 Fixes #66339 Fixes #67019 2019-12-05 01:40:24 -06:00			`// build-pass`

			`// This used to ICE in const-prop`

			`fn foo() {`
			`let bar = \|_\| { };`
Adjust UI tests for `unit_bindings` - Either explicitly annotate `let x: () = expr;` where `x` has unit type, or remove the unit binding to leave only `expr;` instead. - Fix disjoint-capture-in-same-closure test 2023-06-12 03:55:36 -05:00			`bar("a");`
const-prop: Restrict scalar pair propagation We now only propagate a scalar pair if the Rvalue is a tuple with two scalars. This for example avoids propagating a (u8, u8) value when Rvalue has type `((), u8, u8)` (see the regression test). While this is a correct thing to do, implementation is tricky and will be done later. Fixes #66971 Fixes #66339 Fixes #67019 2019-12-05 01:40:24 -06:00			`}`

			`fn main() {`
			`foo();`
			`}`