rust-lang / rust-lang/rust-clippy
if let Some with locked mutex
Open
Nobody has claimed this yet.
A-lint
- Dominant language
- Rust
- Stars
- 13.5k
- Forks
- 2.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 32
Description
What it does
This can cause deadlocks. Similar to #5219 but with locks inside the if clause outside of the else clause.
Advantage
No response
Drawbacks
No response
Example
if let Some(value) = mutex.lock().unwrap().do_something() {
*mutex.lock().unwrap() = new_value();
}
Could be written as:
let value = mutex.lock().unwrap().do_something();
if let Some(value) = value {
*mutex.lock().unwrap() = new_value();
}
or
let guard = mutex.lock().unwrap();
if let Some(value) = guard.do_something() {
*guard = new_value();
}
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing this request with issue #5219 and the two Rust examples showing a mutex lock inside an if-let expression. Trace how an equivalent Clippy lint identifies temporary lock guards, then add coverage for the shown pattern. Done means the problematic form is diagnosed while the explicitly bound alternatives are not.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100