f42fa4f6e0
the `tail-expr-lock-poisoning` UI test uses the `panic::catch_unwind` API so it relies on unwinding being implemented. this test ought not to run on targets that do not support unwinding. add the `needs-unwind` attribute to signal this
31 lines
664 B
Rust
31 lines
664 B
Rust
//@ revisions: edition2021 edition2024
|
|
//@ ignore-wasm no panic or subprocess support
|
|
//@ [edition2024] compile-flags: -Zunstable-options
|
|
//@ [edition2024] edition: 2024
|
|
//@ run-pass
|
|
//@ needs-unwind
|
|
#![cfg_attr(edition2024, feature(shorter_tail_lifetimes))]
|
|
|
|
use std::sync::Mutex;
|
|
|
|
struct PanicOnDrop;
|
|
impl Drop for PanicOnDrop {
|
|
fn drop(&mut self) {
|
|
panic!()
|
|
}
|
|
}
|
|
|
|
fn f(m: &Mutex<i32>) -> i32 {
|
|
let _x = PanicOnDrop;
|
|
*m.lock().unwrap()
|
|
}
|
|
|
|
fn main() {
|
|
let m = Mutex::new(0);
|
|
let _ = std::panic::catch_unwind(|| f(&m));
|
|
#[cfg(edition2024)]
|
|
assert!(m.lock().is_ok());
|
|
#[cfg(edition2021)]
|
|
assert!(m.lock().is_err());
|
|
}
|