rust-lang / rust-lang/rust-clippy

if let Some with locked mutex

Open
#11,773 0 comments 0 reactions 0 assignees View on GitHub

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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.