From 5875ba3364392eb633a3d10ec8faecf706eb46de Mon Sep 17 00:00:00 2001 From: Daniel Silverstone Date: Wed, 19 Dec 2018 20:47:50 +0000 Subject: [PATCH] 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. --- clippy_lints/src/mutex_atomic.rs | 4 ++-- 1 file 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.