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:19: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:20:5
12 20 | 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:21:5
18 21 | 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:23:5
24 23 | 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:24:5
30 24 | 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:25:5
36 25 | 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:26:5
44 26 | Mutex::new(0i32);
47 error: aborting due to 7 previous errors