1 error: Consider using an AtomicBool instead of a Mutex here. If you just want the locking behaviour and not the internal type, consider using Mutex<()>.
2 --> $DIR/mutex_atomic.rs:6:5
7 = note: `-D clippy::mutex-atomic` implied by `-D warnings`
9 error: Consider using an AtomicUsize instead of a Mutex here. If you just want the locking behaviour and not the internal type, consider using Mutex<()>.
10 --> $DIR/mutex_atomic.rs:7:5
12 LL | Mutex::new(5usize);
15 error: Consider using an AtomicIsize instead of a Mutex here. If you just want the locking behaviour and not the internal type, consider using Mutex<()>.
16 --> $DIR/mutex_atomic.rs:8:5
18 LL | Mutex::new(9isize);
21 error: Consider using an AtomicPtr instead of a Mutex here. If you just want the locking behaviour and not the internal type, consider using Mutex<()>.
22 --> $DIR/mutex_atomic.rs:10:5
24 LL | Mutex::new(&x as *const u32);
25 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
27 error: Consider using an AtomicPtr instead of a Mutex here. If you just want the locking behaviour and not the internal type, consider using Mutex<()>.
28 --> $DIR/mutex_atomic.rs:11:5
30 LL | Mutex::new(&mut x as *mut u32);
31 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
33 error: Consider using an AtomicUsize instead of a Mutex here. If you just want the locking behaviour and not the internal type, consider using Mutex<()>.
34 --> $DIR/mutex_atomic.rs:12:5
36 LL | Mutex::new(0u32);
39 = note: `-D clippy::mutex-integer` implied by `-D warnings`
41 error: Consider using an AtomicIsize instead of a Mutex here. If you just want the locking behaviour and not the internal type, consider using Mutex<()>.
42 --> $DIR/mutex_atomic.rs:13:5
44 LL | Mutex::new(0i32);
47 error: aborting due to 7 previous errors