rust/tests/ui/consts/const-eval/issue-64970.rs

//@ run-pass

fn main() {
    foo(10);
}

fn foo(mut n: i32) {
    if false {
        n = 0i32;
    }

    if n > 0i32 {
        let _ = 1i32 / n;
    }
}
[const-prop] Correctly handle locals that can't be propagated `const_prop()` now handles writing the Rvalue into the Place in the stack frame for us. So if we're not supported to propagate that value, we need to clear it. 2019-10-02 05:58:26 -04:00			`//@ run-pass`

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

			`fn foo(mut n: i32) {`
			`if false {`
			`n = 0i32;`
			`}`

			`if n > 0i32 {`
Make error and warning annotations mandatory in UI tests This change makes error and warning annotations mandatory in UI tests. The only exception are tests that use error patterns to match compiler output and don't have any annotations. 2019-11-06 00:00:00 +00:00			`let _ = 1i32 / n;`
[const-prop] Correctly handle locals that can't be propagated `const_prop()` now handles writing the Rvalue into the Place in the stack frame for us. So if we're not supported to propagate that value, we need to clear it. 2019-10-02 05:58:26 -04:00			`}`
			`}`