rust/clippy_lints/src/mutex_atomic.rs

101 lines
3.5 KiB
Rust
Raw Normal View History

2018-10-06 11:18:06 -05:00
// Copyright 2014-2018 The Rust Project Developers. See the COPYRIGHT
// file at the top-level directory of this distribution.
//
// Licensed under the Apache License, Version 2.0 <LICENSE-APACHE or
// http://www.apache.org/licenses/LICENSE-2.0> or the MIT license
// <LICENSE-MIT or http://opensource.org/licenses/MIT>, at your
// option. This file may not be copied, modified, or distributed
// except according to those terms.
2016-07-15 17:25:44 -05:00
//! Checks for uses of mutex where an atomic value could be used
//!
//! This lint is **warn** by default
2018-11-27 14:14:15 -06:00
use crate::rustc::hir::Expr;
use crate::rustc::lint::{LateContext, LateLintPass, LintArray, LintPass};
use crate::rustc::ty::{self, Ty};
2018-11-27 14:14:15 -06:00
use crate::rustc::{declare_tool_lint, lint_array};
use crate::syntax::ast;
2018-05-30 03:15:50 -05:00
use crate::utils::{match_type, paths, span_lint};
/// **What it does:** Checks for usages of `Mutex<X>` where an atomic will do.
2015-12-14 01:03:01 -06:00
///
/// **Why is this bad?** Using a mutex just to make access to a plain bool or
/// reference sequential is shooting flies with cannons.
/// `std::sync::atomic::AtomicBool` and `std::sync::atomic::AtomicPtr` are leaner and
/// faster.
2015-12-14 01:03:01 -06:00
///
/// **Known problems:** This lint cannot detect if the mutex is actually used
/// for waiting before a critical section.
2015-12-14 01:03:01 -06:00
///
2016-07-15 17:25:44 -05:00
/// **Example:**
/// ```rust
/// let x = Mutex::new(&y);
/// ```
2018-03-28 08:24:26 -05:00
declare_clippy_lint! {
pub MUTEX_ATOMIC,
2018-03-28 08:24:26 -05:00
perf,
2016-07-15 17:25:44 -05:00
"using a mutex where an atomic value could be used instead"
}
2017-08-09 02:30:56 -05:00
/// **What it does:** Checks for usages of `Mutex<X>` where `X` is an integral
/// type.
2015-12-14 01:03:01 -06:00
///
2017-08-09 02:30:56 -05:00
/// **Why is this bad?** Using a mutex just to make access to a plain integer
/// sequential is
/// shooting flies with cannons. `std::sync::atomic::AtomicUsize` is leaner and faster.
2015-12-14 01:03:01 -06:00
///
/// **Known problems:** This lint cannot detect if the mutex is actually used
/// for waiting before a critical section.
2015-12-14 01:03:01 -06:00
///
2016-07-15 17:25:44 -05:00
/// **Example:**
/// ```rust
/// let x = Mutex::new(0usize);
/// ```
2018-03-28 08:24:26 -05:00
declare_clippy_lint! {
pub MUTEX_INTEGER,
2018-03-29 06:41:53 -05:00
nursery,
2016-07-15 17:25:44 -05:00
"using a mutex for an integer type"
}
impl LintPass for MutexAtomic {
fn get_lints(&self) -> LintArray {
lint_array!(MUTEX_ATOMIC, MUTEX_INTEGER)
}
}
pub struct MutexAtomic;
impl<'a, 'tcx> LateLintPass<'a, 'tcx> for MutexAtomic {
fn check_expr(&mut self, cx: &LateContext<'a, 'tcx>, expr: &'tcx Expr) {
2017-01-13 10:04:56 -06:00
let ty = cx.tables.expr_ty(expr);
if let ty::Adt(_, subst) = ty.sty {
2016-04-14 11:13:15 -05:00
if match_type(cx, ty, &paths::MUTEX) {
let mutex_param = subst.type_at(0);
if let Some(atomic_name) = get_atomic_name(mutex_param) {
2017-08-09 02:30:56 -05:00
let msg = format!(
"Consider using an {} instead of a Mutex here. If you just want the locking \
2017-09-05 04:33:04 -05:00
behaviour and not the internal type, consider using Mutex<()>.",
2017-08-09 02:30:56 -05:00
atomic_name
);
match mutex_param.sty {
ty::Uint(t) if t != ast::UintTy::Usize => span_lint(cx, MUTEX_INTEGER, expr.span, &msg),
ty::Int(t) if t != ast::IntTy::Isize => span_lint(cx, MUTEX_INTEGER, expr.span, &msg),
2016-01-03 22:26:12 -06:00
_ => span_lint(cx, MUTEX_ATOMIC, expr.span, &msg),
2015-12-31 14:39:03 -06:00
};
}
}
}
}
}
2018-07-23 06:01:12 -05:00
fn get_atomic_name(ty: Ty<'_>) -> Option<(&'static str)> {
match ty.sty {
ty::Bool => Some("AtomicBool"),
ty::Uint(_) => Some("AtomicUsize"),
ty::Int(_) => Some("AtomicIsize"),
ty::RawPtr(_) => Some("AtomicPtr"),
2016-01-03 22:26:12 -06:00
_ => None,
}
}