run test one by one (#43) #183
clippy
6 warnings
Details
Results
| Message level | Amount |
|---|---|
| Internal compiler error | 0 |
| Error | 0 |
| Warning | 6 |
| Note | 0 |
| Help | 0 |
Versions
- rustc 1.59.0-nightly (34926f0a1 2021-12-22)
- cargo 1.59.0-nightly (fcef61230 2021-12-17)
- clippy 0.1.59 (34926f0 2021-12-22)
Annotations
Check warning on line 22 in src/stop.rs
github-actions / clippy
consider using an `AtomicBool` instead of a `Mutex` here; if you just want the locking behavior and not the internal type, consider using `Mutex<()>`
warning: consider using an `AtomicBool` instead of a `Mutex` here; if you just want the locking behavior and not the internal type, consider using `Mutex<()>`
--> src/stop.rs:22:25
|
22 | let mut inner = self.inner.lock().unwrap();
| ^^^^^^^^^^
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#mutex_atomic
Check warning on line 16 in src/stop.rs
github-actions / clippy
consider using an `AtomicBool` instead of a `Mutex` here; if you just want the locking behavior and not the internal type, consider using `Mutex<()>`
warning: consider using an `AtomicBool` instead of a `Mutex` here; if you just want the locking behavior and not the internal type, consider using `Mutex<()>`
--> src/stop.rs:16:25
|
16 | let mut inner = self.inner.lock().unwrap();
| ^^^^^^^^^^
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#mutex_atomic
Check warning on line 11 in src/stop.rs
github-actions / clippy
consider using an `AtomicBool` instead of a `Mutex` here; if you just want the locking behavior and not the internal type, consider using `Mutex<()>`
warning: consider using an `AtomicBool` instead of a `Mutex` here; if you just want the locking behavior and not the internal type, consider using `Mutex<()>`
--> src/stop.rs:11:20
|
11 | inner: Mutex::new(false),
| ^^^^^^^^^^^^^^^^^
|
= note: `#[warn(clippy::mutex_atomic)]` on by default
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#mutex_atomic
Check warning on line 22 in src/stop.rs
github-actions / clippy
consider using an `AtomicBool` instead of a `Mutex` here; if you just want the locking behavior and not the internal type, consider using `Mutex<()>`
warning: consider using an `AtomicBool` instead of a `Mutex` here; if you just want the locking behavior and not the internal type, consider using `Mutex<()>`
--> src/stop.rs:22:25
|
22 | let mut inner = self.inner.lock().unwrap();
| ^^^^^^^^^^
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#mutex_atomic
Check warning on line 16 in src/stop.rs
github-actions / clippy
consider using an `AtomicBool` instead of a `Mutex` here; if you just want the locking behavior and not the internal type, consider using `Mutex<()>`
warning: consider using an `AtomicBool` instead of a `Mutex` here; if you just want the locking behavior and not the internal type, consider using `Mutex<()>`
--> src/stop.rs:16:25
|
16 | let mut inner = self.inner.lock().unwrap();
| ^^^^^^^^^^
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#mutex_atomic
Check warning on line 11 in src/stop.rs
github-actions / clippy
consider using an `AtomicBool` instead of a `Mutex` here; if you just want the locking behavior and not the internal type, consider using `Mutex<()>`
warning: consider using an `AtomicBool` instead of a `Mutex` here; if you just want the locking behavior and not the internal type, consider using `Mutex<()>`
--> src/stop.rs:11:20
|
11 | inner: Mutex::new(false),
| ^^^^^^^^^^^^^^^^^
|
= note: `#[warn(clippy::mutex_atomic)]` on by default
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#mutex_atomic