Clippy lints / Style
Clippy lint · Style · checked with Clippy 0.1.99
clippy::to_string_trait_impl: direct implementation of `ToString`
What it meansChecks for direct implementations of ToString. It is in the style group and warns by default.
What you see
warning: direct implementation of `ToString` --> main.rs:8:1 | 8 | / impl ToString for Point { 9 | | fn to_string(&self) -> String { 10 | | format!("({}, {})", self.x, self.y) 11 | | } 12 | | } | |_^ | = help: prefer implementing `Display` instead = help: for further information visit https://rust-lang.github.io/rust-clippy/stable/index.html#to_string_trait_impl = note: `#[warn(clippy::to_string_trait_impl)]` on by default
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?
This trait is automatically implemented for any type which implements the Display trait. As such, ToString shouldn’t be implemented directly: Display should be implemented instead, and you get the ToString implementation for free.
Code that works but is not idiomatic Rust. Warns by default.
How to fix it
Clippy does not fix this one automatically. Change the code by hand:
Flagged
struct Point {
x: usize,
y: usize,
}
impl ToString for Point {
fn to_string(&self) -> String {
format!("({}, {})", self.x, self.y)
}
}
Write this instead
struct Point {
x: usize,
y: usize,
}
impl std::fmt::Display for Point {
fn fmt(&self, f: &mut std::fmt::Formatter<'_>) -> std::fmt::Result {
write!(f, "({}, {})", self.x, self.y)
}
}
Turn it off, or on
Allow it where it does not fit your code, as narrowly as you can:
On one item
#[allow(clippy::to_string_trait_impl)]
fn my_function() { /* ... */ }Whole crate (Cargo.toml)
[lints.clippy]
to_string_trait_impl = "allow"One run
cargo clippy -- -A clippy::to-string-trait-implThe [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 direct implementations of ToString.
Why is this bad?
This trait is automatically implemented for any type which implements the Display trait.
As such, ToString shouldn’t be implemented directly: Display should be implemented instead,
and you get the ToString implementation for free.
Example
struct Point {
x: usize,
y: usize,
}
impl ToString for Point {
fn to_string(&self) -> String {
format!("({}, {})", self.x, self.y)
}
}
Use instead:
struct Point {
x: usize,
y: usize,
}
impl std::fmt::Display for Point {
fn fmt(&self, f: &mut std::fmt::Formatter<'_>) -> std::fmt::Result {
write!(f, "({}, {})", self.x, self.y)
}
}
From the Clippy lint list (0.1.99), part of the Rust project, MIT or Apache-2.0. Official entry.
Related lints
- needless_returnunneeded `return` statement
- new_without_defaultChecks for public types with a pub fn new() -> Self method and no implementation of Default
- len_zeroChecks for getting the length of something via .len() just to compare to zero, and suggests using .is_empty() where applicable
- string_extend_charscalling `.extend(_.chars())`
- tabs_in_doc_commentsusing tabs in doc comments is not recommended
- to_digit_is_someChecks for .to_digit(..).is_some() on chars
- toplevel_ref_arg`ref` directly on a function parameter does not prevent taking ownership of the passed argument. Consider using a reference type instead
- trim_split_whitespacefound call to `str::trim` before `str::split_whitespace`
- unnecessary_fallible_conversionsuse of a fallible conversion when an infallible one could be used
All 847 Clippy lints · Rust compiler errors · Cargo.toml checker
Up next
Related lintclippy::needless_returnunneeded `return` statementRead it next →Did this answer your question?