Clippy lints / Restriction
Clippy lint · Restriction · checked with Clippy 0.1.99
clippy::pathbuf_init_then_push: Checks for calls to push immediately after creating a new PathBuf
What it meansChecks for calls to push immediately after creating a new PathBuf. It is in the restriction group and off by default.
Does it matter?
Multiple .join() calls are usually easier to read than multiple .push calls across multiple statements. It might also be possible to use PathBuf::from instead.
Lints that forbid language features for specific codebases (no unwrap, no indexing...). Off by default; pick them one by one, never the whole group.
How to fix it
Clippy does not fix this one automatically (its suggestion may change behaviour, so it only shows it). Change the code by hand:
Flagged
let mut path_buf = PathBuf::new();
path_buf.push("foo");
Write this instead
let path_buf = PathBuf::from("foo");
// or
let path_buf = PathBuf::new().join("foo");
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]
pathbuf_init_then_push = "warn"In code
#![warn(clippy::pathbuf_init_then_push)]One run
cargo clippy -- -W clippy::pathbuf-init-then-pushThe [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 calls to push immediately after creating a new PathBuf.
Why is this bad?
Multiple .join() calls are usually easier to read than multiple .push
calls across multiple statements. It might also be possible to use
PathBuf::from instead.
Known problems
.join() introduces an implicit clone(). PathBuf::from can alternatively be
used when the PathBuf is newly constructed. This will avoid the implicit clone.
Example
let mut path_buf = PathBuf::new();
path_buf.push("foo");
Use instead:
let path_buf = PathBuf::from("foo");
// or
let path_buf = PathBuf::new().join("foo");
From the Clippy lint list (0.1.99), part of the Rust project, MIT or Apache-2.0. Official entry.
Related lints
- unwrap_usedChecks for .unwrap() or .unwrap_err() calls on Results and .unwrap() call on Options
- module_name_repetitionsDetects public item names that are prefixed or suffixed by the containing public module’s name
- expect_usedChecks for .expect() or .expect_err() calls on Results and .expect() call on Options
- panic`panic` should not be present in production code
- panic_in_result_fnused `panic!()` or assertion in a function that returns `Result`
- partial_pub_fieldsmixed usage of pub and non-pub fields
- pattern_type_mismatchtype of pattern does not match the expression type
- pointer_formatpointer formatting detected
- precedence_bitsChecks for bit shifting operations combined with bit masking/combining operators and suggest using parentheses
All 847 Clippy lints · Rust compiler errors · Cargo.toml checker
Up next
Related lintclippy::unwrap_usedChecks for .unwrap() or .unwrap_err() calls on Results and .unwrap() call on OptionsRead it next →Did this answer your question?