Clippy lints / Nursery
Clippy lint · Nursery · checked with Clippy 0.1.99
clippy::literal_string_with_formatting_args: this looks like a formatting argument but it is not part of a formatting macro
What it meansChecks if string literals have formatting arguments outside of macros using them (like format!). It is in the nursery group and off by default.
What you see
warning: this looks like a formatting argument but it is not part of a formatting macro --> main.rs:5:11 | 5 | x.expect("{y:?}"); | ^^^^^ | = help: for further information visit https://rust-lang.github.io/rust-clippy/stable/index.html#literal_string_with_formatting_args = note: `-W clippy::literal-string-with-formatting-args` implied by `-W clippy::nursery`
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 will likely not generate the expected content.
New lints still being finished. Off by default and may have false positives.
How to fix it
Clippy does not fix this one automatically. Change the code by hand:
Flagged
let x: Option<usize> = None;
let y = "hello";
x.expect("{y:?}");
Write this instead
let x: Option<usize> = None;
let y = "hello";
x.expect(&format!("{y:?}"));
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]
literal_string_with_formatting_args = "warn"In code
#![warn(clippy::literal_string_with_formatting_args)]One run
cargo clippy -- -W clippy::literal-string-with-formatting-argsThe [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 if string literals have formatting arguments outside of macros
using them (like format!).
Why is this bad?
It will likely not generate the expected content.
Example
let x: Option<usize> = None;
let y = "hello";
x.expect("{y:?}");
Use instead:
let x: Option<usize> = None;
let y = "hello";
x.expect(&format!("{y:?}"));
From the Clippy lint list (0.1.99), part of the Rust project, MIT or Apache-2.0. Official entry.
Related lints
- redundant_cloneChecks for a redundant clone() (and its relatives) which clones an owned value that is going to be dropped without further use
- iter_on_single_items`iter` call on a collection with only one item
- iter_with_drainChecks for usage of .drain(..) on Vec and VecDeque for iteration
- large_stack_framesChecks for functions that use a lot of stack space. This often happens when constructing a large type, such as an array with a lot of elements, or constructing many smaller-but-still-large structs, or copying around a lot of large types. This lint is a more general version of large_stack_arrays that is intended to look at functions as a whole instead of only individual array expressions inside of a function
- missing_const_for_fnthis could be a `const fn`
- needless_collectChecks for functions collecting an iterator when collect is not needed
- needless_pass_by_ref_mutthis parameter is a mutable reference but is not used mutably
All 847 Clippy lints · Rust compiler errors · Cargo.toml checker
Up next
Related lintclippy::redundant_cloneChecks for a redundant clone() (and its relatives) which clones an owned value that is going to be dropped without further useRead it next →Did this answer your question?