rust/tests/ui/mutex_atomic.rs

27 lines
1.2 KiB
Rust
Raw Normal View History

2018-07-28 10:34:52 -05:00
#![warn(clippy::all)]
#![warn(clippy::mutex_integer)]
2022-01-10 08:36:13 -06:00
#![warn(clippy::mutex_atomic)]
#![allow(clippy::borrow_as_ptr)]
fn main() {
use std::sync::Mutex;
2017-02-08 07:58:07 -06:00
Mutex::new(true);
//~^ ERROR: consider using an `AtomicBool` instead of a `Mutex` here; if you just want
//~| NOTE: `-D clippy::mutex-atomic` implied by `-D warnings`
2017-02-08 07:58:07 -06:00
Mutex::new(5usize);
//~^ ERROR: consider using an `AtomicUsize` instead of a `Mutex` here; if you just wan
2017-02-08 07:58:07 -06:00
Mutex::new(9isize);
//~^ ERROR: consider using an `AtomicIsize` instead of a `Mutex` here; if you just wan
let mut x = 4u32;
2017-02-08 07:58:07 -06:00
Mutex::new(&x as *const u32);
//~^ ERROR: consider using an `AtomicPtr` instead of a `Mutex` here; if you just want
2017-02-08 07:58:07 -06:00
Mutex::new(&mut x as *mut u32);
//~^ ERROR: consider using an `AtomicPtr` instead of a `Mutex` here; if you just want
2017-02-08 07:58:07 -06:00
Mutex::new(0u32);
//~^ ERROR: consider using an `AtomicUsize` instead of a `Mutex` here; if you just wan
//~| NOTE: `-D clippy::mutex-integer` implied by `-D warnings`
2017-02-08 07:58:07 -06:00
Mutex::new(0i32);
//~^ ERROR: consider using an `AtomicIsize` instead of a `Mutex` here; if you just wan
Mutex::new(0f32); // there are no float atomics, so this should not lint
}