rust-lang / rust-lang/rust-clippy
lint mixed volatile and unsynced access
Open
Nobody has claimed this yet.
A-lint
E-medium
T-middle
- Dominant language
- Rust
- Stars
- 13.5k
- Forks
- 2.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 32
Description
this voids any synchonization guarantees the volatile accesses should uphold.
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
The issue names no file, test, or entry point, so first locate the relevant Clippy lint area and clarify the intended behavior for mixed volatile and unsynchronized access. Done should mean the lint reliably identifies this combination without voiding the synchronization guarantees described in the issue, with tests covering the expected cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100