rust-lang / rust-lang/rust-clippy
Lint for `fold` closure that never moves the accumulator
Open
@jdupak is already working on this.
Since May 15, 2025.
A-lint
good first issue
L-perf
- Dominant language
- Rust
- Stars
- 13.5k
- Forks
- 2.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 32
Description
What it does
Lint when a fold closure always returns the accumulator from the input, having only used it by reference. (As opposed to consuming the accumulator, or returning something else.)
Categories (optional)
- Kind:
perf
The compiler currently cannot always optimize away passing along the accumulator every time (see https://github.com/rust-lang/rust/issues/76725), so it's better to not do that if it's actually the same thing every time anyway.
Drawbacks
None.
(Well, it leaves something mut, but that's easily fixable with let v = v;.)
Example
let word = word.to_lowercase();
let char_count: HashMap<char, usize> = word.chars().fold(HashMap::new(), |mut chars, c| {
*chars.entry(c).or_default() += 1;
chars
});
Could be written as:
let word = word.to_lowercase();
let mut char_count: HashMap<char, usize> = HashMap::new();
word.chars().for_each(|c| *chars.entry(c).or_default() += 1);
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.
Assessment
This issue has not been assessed yet.