Clippy lints / Restriction
Clippy lint · Restriction · checked with Clippy 0.1.99
clippy::rc_mutex: Checks for Rc<Mutex<T>>
What it meansChecks for Rc<Mutex<T>>. It is in the restriction group and off by default.
Does it matter?
Rc is used in single thread and Mutex is used in multi thread. Consider using Rc<RefCell<T>> in single thread or Arc<Mutex<T>> in multi thread.
Lints that forbid language features for specific codebases (no unwrap, no indexing...). Off by default; pick them one by one, never the whole group.
How to fix it
Clippy does not fix this one automatically. Change the code by hand:
Flagged
use std::rc::Rc;
use std::sync::Mutex;
fn foo(interned: Rc<Mutex<i32>>) { ... }
Write this instead
use std::rc::Rc;
use std::cell::RefCell
fn foo(interned: Rc<RefCell<i32>>) { ... }
Turn it off, or on
It is off by default. To use it, set it to warn or deny:
Whole crate (Cargo.toml)
[lints.clippy]
rc_mutex = "warn"In code
#![warn(clippy::rc_mutex)]One run
cargo clippy -- -W clippy::rc-mutexThe [lints] table needs Rust 1.74 or newer. In a workspace, put it under [workspace.lints.clippy] and add [lints] workspace = true to each member.
Settings in clippy.toml
avoid-breaking-exported-api: Suppress lints whenever the suggested change would cause breakage for other crates.
Clippy's own documentation
What it does
Checks for Rc<Mutex<T>>.
Why restrict this?
Rc is used in single thread and Mutex is used in multi thread.
Consider using Rc<RefCell<T>> in single thread or Arc<Mutex<T>> in multi thread.
Known problems
Sometimes combining generic types can lead to the requirement that a type use Rc in conjunction with Mutex. We must consider those cases false positives, but alas they are quite hard to rule out. Luckily they are also rare.
Example
use std::rc::Rc;
use std::sync::Mutex;
fn foo(interned: Rc<Mutex<i32>>) { ... }
Better:
use std::rc::Rc;
use std::cell::RefCell
fn foo(interned: Rc<RefCell<i32>>) { ... }
Configuration
-
avoid-breaking-exported-api: Suppress lints whenever the suggested change would cause breakage for other crates.(default:
true)
From the Clippy lint list (0.1.99), part of the Rust project, MIT or Apache-2.0. Official entry.
Related lints
- unwrap_usedChecks for .unwrap() or .unwrap_err() calls on Results and .unwrap() call on Options
- module_name_repetitionsDetects public item names that are prefixed or suffixed by the containing public module’s name
- expect_usedChecks for .expect() or .expect_err() calls on Results and .expect() call on Options
- pub_without_shorthandusage of `pub` with `in`
- question_mark_usedChecks for expressions that use the ? operator and rejects them
- rc_bufferChecks for Rc<T> and Arc<T> when T is a mutable buffer type such as String or Vec
- redundant_test_prefixChecks for test functions (functions annotated with #[test]) that are prefixed with test_ which is redundant
- redundant_type_annotationsredundant type annotation
- ref_patternsusage of ref pattern
All 847 Clippy lints · Rust compiler errors · Cargo.toml checker
Up next
Related lintclippy::unwrap_usedChecks for .unwrap() or .unwrap_err() calls on Results and .unwrap() call on OptionsRead it next →Did this answer your question?