rust-lang / rust-lang/rust-clippy
Suggest replacing 'iter().any(|x| x == y)' with 'contains' where appropriate
Open
Nobody has claimed this yet.
A-lint
L-perf
L-unnecessary
T-middle
- Dominant language
- Rust
- Stars
- 13.5k
- Forks
- 2.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 32
Description
Particularly for str.chars().any or types with non-default implementations of SliceContains.
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 by reviewing the issue's proposed iter().any(|x| x == y) pattern, especially str.chars().any and types with non-default SliceContains implementations. Determine the appropriate lint scope and exclusions; done means the behavior is specified and the relevant Clippy lint changes are 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