rust-lang / rust-lang/rust-clippy
`result` should not be used as parameter
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
Detect a parameter named as result
Inspired by result keyword in why3
Advantage
resultas a paramter is quite strange
Drawbacks
None
Example
fn foo(result : u8) {}
Could be written as:
fn foo(x : u8) {}
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 files or tests, so start by locating how rust-clippy defines and tests lints for parameter names. Use the provided fn foo(result: u8) {} example as the initial case; done means a parameter named result is detected and the case is covered by tests.
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