rust-lang / rust-lang/rust-clippy
Lint to suggest String::as_str or Vec::as_slice
Open
Nobody has claimed this yet.
A-lint
E-medium
L-restriction
T-middle
- Dominant language
- Rust
- Stars
- 13.5k
- Forks
- 2.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 32
Description
Right now, it's common for people to write map(|s| &**s) or map(|s| &*s) when map(String::as_str) or map(Vec::as_slice) might be clearer.
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
No files, tests, or entry points are named in the issue. Start by locating existing Clippy lints that recognize map expressions and their corresponding tests; done means the lint suggests String::as_str or Vec::as_slice for the shown patterns with appropriate test coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100