Clippy lints / Pedantic
Clippy lint · Pedantic · checked with Clippy 0.1.99
clippy::non_std_lazy_statics: Lints when once_cell::sync::Lazy or lazy_static! are used to define a static variable, and suggests replacing such cases with std::sync::LazyLock instead. Note: This lint will not trigger in crate with no_std context, or with MSRV < 1.80.0
What it meansLints when once_cell::sync::Lazy or lazy_static! are used to define a static variable, and suggests replacing such cases with std::sync::LazyLock instead. Note: This lint will not trigger in crate with no_std context, or with MSRV < 1.80.0. It also will not trigger on once_cell::sync::Lazy usage in crates which use other types from once_cell, such as once_cell::race::OnceBox. It is in the pedantic group and off by default.
Does it matter?
Reduces the need for an extra dependency Enforce convention of using standard library types when possible
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
lazy_static! {
static ref FOO: String = "foo".to_uppercase();
}
static BAR: once_cell::sync::Lazy<String> = once_cell::sync::Lazy::new(|| "BAR".to_lowercase());
Write this instead
static FOO: std::sync::LazyLock<String> = std::sync::LazyLock::new(|| "FOO".to_lowercase());
static BAR: std::sync::LazyLock<String> = std::sync::LazyLock::new(|| "BAR".to_lowercase());
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]
non_std_lazy_statics = "warn"In code
#![warn(clippy::non_std_lazy_statics)]One run
cargo clippy -- -W clippy::non-std-lazy-staticsThe [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.
Settings in clippy.toml
msrv: The minimum rust version that the project supports. Defaults to the rust-version field in Cargo.toml
Clippy's own documentation
What it does
Lints when once_cell::sync::Lazy or lazy_static! are used to define a static variable,
and suggests replacing such cases with std::sync::LazyLock instead.
Note: This lint will not trigger in crate with no_std context, or with MSRV < 1.80.0. It
also will not trigger on once_cell::sync::Lazy usage in crates which use other types
from once_cell, such as once_cell::race::OnceBox.
Why restrict this?
- Reduces the need for an extra dependency
- Enforce convention of using standard library types when possible
Example
lazy_static! {
static ref FOO: String = "foo".to_uppercase();
}
static BAR: once_cell::sync::Lazy<String> = once_cell::sync::Lazy::new(|| "BAR".to_lowercase());
Use instead:
static FOO: std::sync::LazyLock<String> = std::sync::LazyLock::new(|| "FOO".to_lowercase());
static BAR: std::sync::LazyLock<String> = std::sync::LazyLock::new(|| "BAR".to_lowercase());
Configuration
-
msrv: The minimum rust version that the project supports. Defaults to therust-versionfield inCargo.toml(default:
current version)
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
- needless_raw_string_hashesunnecessary hashes around raw string literal
- no_effect_underscore_bindingbinding to `_` prefixed variable with no side-effect
- no_mangle_with_rust_abi`#[no_mangle]` set on a function with the default (`Rust`) ABI
- nonminimal_boolChecks for boolean expressions that can be written more concisely
- option_as_ref_clonedcloning an `Option<_>` using `.as_ref().cloned()`
- option_optionuse of `Option<Option<T>>`
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?