rust-lang / rust-lang/rust-clippy
Suggestion: borrowing a RefCell in funarg position
Open
Nobody has claimed this yet.
A-lint
good first issue
T-middle
- Dominant language
- Rust
- Stars
- 13.5k
- Forks
- 2.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 32
Description
I recently came across this fun correctness bug in my code: https://github.com/rust-lang/rust/issues/65086.
I’m not sure how I could have known this without asking a compiler developer. Can we add a lint prohibiting RefCell borrows in funarg position since they prevent mutable borrows further down the stack?
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 with the linked rust-lang/rust issue #65086 to understand the reported RefCell behavior and review Clippy's existing lint conventions. The issue does not name an entry point or tests; completion would require an agreed lint scope and corresponding implementation and validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100