rust-lang / rust-lang/rust-clippy
review all `expr_ty` calls
Open
Nobody has claimed this yet.
C-enhancement
E-hard
L-correctness
- Dominant language
- Rust
- Stars
- 13.5k
- Forks
- 2.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 32
Description
Often they should be expr_ty_adjusted.
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
Search the rust-clippy codebase for every expr_ty call and compare each use with expr_ty_adjusted. Determine which calls should use the adjusted form; done means the relevant calls have been reviewed and any necessary changes are complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100