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();
}
[AUTO-GENERATED] Migrate ui tests from `//` to `//@` directives 2024-02-16 20:02:50 +00:00			`//@ compile-flags: -Z mir-opt-level=3`
			`//@ build-pass`
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 10:40:24 +03:00
			`// 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 16:55:36 +08: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 10:40:24 +03:00			`}`

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