Clippy lints / Pedantic
Clippy lint · Pedantic · checked with Clippy 0.1.99
clippy::default_trait_access: calling `String::default()` is more clear than this expression
What it meansChecks for literal calls to Default::default(). It is in the pedantic group and off by default.
What you see
warning: calling `String::default()` is more clear than this expression --> main.rs:3:17 | 3 | let s: String = Default::default(); | ^^^^^^^^^^^^^^^^^^ help: try: `String::default()` | = help: for further information visit https://rust-lang.github.io/rust-clippy/stable/index.html#default_trait_access = note: `-W clippy::default-trait-access` 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?
It’s easier for the reader if the name of the type is used, rather than the generic Default.
Stricter lints with some false positives. Off by default; opt in with clippy::pedantic.
How to fix it
Clippy does not fix this one automatically. Change the code by hand:
Flagged
let s: String = Default::default();
Write this instead
let s = String::default();
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]
default_trait_access = "warn"In code
#![warn(clippy::default_trait_access)]One run
cargo clippy -- -W clippy::default-trait-accessThe [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 literal calls to Default::default().
Why is this bad?
It’s easier for the reader if the name of the type is used, rather than the
generic Default.
Example
let s: String = Default::default();
Use instead:
let s = String::default();
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
- comparison_chainChecks comparison chains written with if that can be rewritten with match and cmp
- copy_iteratorChecks for types that implement Copy as well as Iterator
- decimal_bitwise_operandsusing decimal literal for bitwise operation
- doc_broken_linkpossible broken doc link: broken across multiple lines
- doc_comment_double_space_linebreaksDetects doc comments that use double spaces as hard line break, instead of backslash (\)
- doc_link_with_quotespossible intra-doc link using quotes instead of backticks
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?