about summary refs log tree commit diff
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2018-12-19 20:54:48 +0000
committerbors <bors@rust-lang.org>2018-12-19 20:54:48 +0000
commitf067c5c1eca0b67cd65ff5e782f8a6fc003c5930 (patch)
treecd3e0ea483441bddb3fce7f02feeb4040d2430d6
parent691e5e76d3e8623e59f37c227d47b67e4913c1d1 (diff)
parent5875ba3364392eb633a3d10ec8faecf706eb46de (diff)
downloadrust-f067c5c1eca0b67cd65ff5e782f8a6fc003c5930.tar.gz
rust-f067c5c1eca0b67cd65ff5e782f8a6fc003c5930.zip
Auto merge of #3566 - kinnison:kinnison/typofix, r=phansch
mutex_atomic: Correct location of AtomicBool and friends

The AtomicBool, AtomicUsize, and friends, types live in the
`std::sync::atomic` module, rather than `std::atomic` as the lint
help text used to say.
-rw-r--r--clippy_lints/src/mutex_atomic.rs4
1 files changed, 2 insertions, 2 deletions
diff --git a/clippy_lints/src/mutex_atomic.rs b/clippy_lints/src/mutex_atomic.rs
index 34683934eca..fb467d886b5 100644
--- a/clippy_lints/src/mutex_atomic.rs
+++ b/clippy_lints/src/mutex_atomic.rs
@@ -22,7 +22,7 @@ use crate::utils::{match_type, paths, span_lint};
 ///
 /// **Why is this bad?** Using a mutex just to make access to a plain bool or
 /// reference sequential is shooting flies with cannons.
-/// `std::atomic::AtomicBool` and `std::atomic::AtomicPtr` are leaner and
+/// `std::sync::atomic::AtomicBool` and `std::sync::atomic::AtomicPtr` are leaner and
 /// faster.
 ///
 /// **Known problems:** This lint cannot detect if the mutex is actually used
@@ -43,7 +43,7 @@ declare_clippy_lint! {
 ///
 /// **Why is this bad?** Using a mutex just to make access to a plain integer
 /// sequential is
-/// shooting flies with cannons. `std::atomic::usize` is leaner and faster.
+/// shooting flies with cannons. `std::sync::atomic::AtomicUsize` is leaner and faster.
 ///
 /// **Known problems:** This lint cannot detect if the mutex is actually used
 /// for waiting before a critical section.