rust/tests/ui/coroutine/drop-and-replace.rs

46 lines
1021 B
Rust
Raw Normal View History

// run-pass
2019-05-22 17:17:38 -05:00
// Regression test for incorrect DropAndReplace behavior introduced in #60840
// and fixed in #61373. When combined with the optimization implemented in
2023-10-19 16:46:28 -05:00
// #60187, this produced incorrect code for coroutines when a saved local was
2019-05-22 17:17:38 -05:00
// re-assigned.
2023-10-19 16:46:28 -05:00
#![feature(coroutines, coroutine_trait)]
2019-05-22 17:17:38 -05:00
2023-10-19 11:06:43 -05:00
use std::ops::{Coroutine, CoroutineState};
2019-05-22 17:17:38 -05:00
use std::pin::Pin;
#[derive(Debug, PartialEq)]
struct Foo(i32);
impl Drop for Foo {
2023-10-19 11:06:43 -05:00
fn drop(&mut self) {}
2019-05-22 17:17:38 -05:00
}
fn main() {
let mut a = || {
let mut x = Foo(4);
yield;
assert_eq!(x.0, 4);
// At one point this tricked our dataflow analysis into thinking `x` was
// StorageDead after the assignment.
x = Foo(5);
assert_eq!(x.0, 5);
{
let y = Foo(6);
yield;
assert_eq!(y.0, 6);
}
assert_eq!(x.0, 5);
};
loop {
match Pin::new(&mut a).resume(()) {
2023-10-19 11:06:43 -05:00
CoroutineState::Complete(()) => break,
2019-05-22 17:17:38 -05:00
_ => (),
}
}
}