rust-lang / rust-lang/rust-clippy
New lint: `a = b.splice(.., a).collect()`
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 13.5k
- Forks
- 2.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 32
Description
What it does
Lint usages of Vec::splice in the form of a = b.splice(.., a).collect() or a = b.splice(..b.len(), a).collect() that can be written mem::swap(&mut a, &mut b).
Lint Name
splice_instead_of_swap
Category
style, complexity, perf
Advantage
Less readable than mem::swap(&mut a, &mut b).
Drawbacks
I'm not sure if anybody has ever made this mistake, I think it's very rare.
Example
let a = vec![1, 2, 3];
let mut b = vec![10, 20, 30];
a = b.splice(.., a).collect();
Could be written as:
let mut a = vec![1, 2, 3];
let mut b = vec![10, 20, 30];
std::mem::swap(&mut a, &mut b);
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 locating the implementation and tests for the splice_instead_of_swap lint, then compare them with the issue's two Vec::splice patterns. Done means the lint recognizes both equivalent forms, suggests std::mem::swap(&mut a, &mut b), and covers the behavior with 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
- 48/100