Clippy lints / Pedantic
Clippy lint · Pedantic · checked with Clippy 0.1.99
clippy::unnecessary_join: called `.collect::<Vec<String>>().join("")` on an iterator
What it meansChecks for usage of .collect::<Vec<String>>().join("") on iterators. It is in the pedantic group and off by default.
What you see
warning: called `.collect::<Vec<String>>().join("")` on an iterator --> main.rs:4:60 | 4 | let output = vector.iter().map(|item| item.to_uppercase()).collect::<Vec<String>>().join(""); | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: consider using: `collect::<String>()` | = help: for further information visit https://rust-lang.github.io/rust-clippy/stable/index.html#unnecessary_join = note: `-W clippy::unnecessary-join` implied by `-W clippy::pedantic`
Real output of Clippy 0.1.99 (Rust 1.99) on the example below. Names and line numbers in yours will differ.
Does it matter?
.collect::<String>() is more concise and might be more performant
Stricter lints with some false positives. Off by default; opt in with clippy::pedantic.
How to fix it
Clippy can fix this one for you: run cargo clippy --fix (add --allow-dirty if you have uncommitted changes). Review the diff before you commit.
Flagged
let vector = vec!["hello", "world"];
let output = vector.iter().map(|item| item.to_uppercase()).collect::<Vec<String>>().join("");
println!("{}", output);
Write this instead
let vector = vec!["hello", "world"];
let output = vector.iter().map(|item| item.to_uppercase()).collect::<String>();
println!("{}", output);
Turn it off, or on
It is off by default. To use it, set it to warn or deny:
Whole crate (Cargo.toml)
[lints.clippy]
unnecessary_join = "warn"In code
#![warn(clippy::unnecessary_join)]One run
cargo clippy -- -W clippy::unnecessary-joinThe [lints] table needs Rust 1.74 or newer. In a workspace, put it under [workspace.lints.clippy] and add [lints] workspace = true to each member.
Clippy's own documentation
What it does
Checks for usage of .collect::<Vec<String>>().join("") on iterators.
Why is this bad?
.collect::<String>() is more concise and might be more performant
Example
let vector = vec!["hello", "world"];
let output = vector.iter().map(|item| item.to_uppercase()).collect::<Vec<String>>().join("");
println!("{}", output);
The correct use would be:
let vector = vec!["hello", "world"];
let output = vector.iter().map(|item| item.to_uppercase()).collect::<String>();
println!("{}", output);
Known problems
While .collect::<String>() is sometimes more performant, there are cases where
using .collect::<String>() over .collect::<Vec<String>>().join("")
will prevent loop unrolling and will result in a negative performance impact.
Additionally, differences have been observed between aarch64 and x86_64 assembly output,
with aarch64 tending to producing faster assembly in more cases when using .collect::<String>()
From the Clippy lint list (0.1.99), part of the Rust project, MIT or Apache-2.0. Official entry.
Related lints
- too_many_linesChecks for functions with a large amount of lines
- missing_errors_docChecks the doc comments of publicly visible functions that return a Result type and warns if there is no # Errors section
- must_use_candidateChecks for public functions that have no #[must_use] attribute, but return something not already marked must-use, have no mutable arg and mutate no statics
- uninlined_format_argsDetect when a variable is not inlined in a format string, and suggests to inline it
- unnecessary_box_returnsboxed return of the sized type `std::string::String`
- unnecessary_debug_formattingChecks for Debug formatting ({:?}) applied to an OsStr or Path. This includes: Format specifiers on format_args!() (width, precision have no effect) Format width too small for the format trait (e.g
- unnecessary_literal_boundDetects functions that are written to return &str that could return &'static str but instead return a &'a str
- unnecessary_semicolonChecks for the presence of a semicolon at the end of a match or if statement evaluating to ()
- unnecessary_trailing_commaunnecessary trailing comma
All 847 Clippy lints · Rust compiler errors · Cargo.toml checker
Up next
Related lintclippy::too_many_linesChecks for functions with a large amount of linesRead it next →Did this answer your question?