Chapter 02

Clippy documentation can be found here (opens in a new tab).

2.1 Why care about linting?

Rust compiler is a powerful tool that catches many mistakes. However, some more in-depth analysis require extra tools, that is where cargo clippy clippy comes into to play. Clippy checks for:

• Performance pitfalls.
• Style issues.
• Redundant code.
• Potential bugs.
• Non-idiomatic Rust.

2.2 Always run cargo clippy

Add the following to your daily workflow:

• --all-targets: checks library, tests, benches and examples.
• --all-features: checks code for all features enabled, auto solves conflicting features.
• --locked: Requires Cargo.lock to be up-to-date, can be solved with $ cargo update.
• -D warnings: treats warnings as errors

Potential additions elements to add:

• -- -W clippy::pedantic: lints which are rather strict or have occasional false positives.
• -- -W clippy::nursery: Optionally can be added to check for new lints that are still under development.
• ❗ Add this to your Makefile, Justfile, xtask or CI Pipeline.

Example at ApolloGraphQL

In the Router project there is a xtask configured for linting that can be executed with cargo xtask lint.

2.3 Important Clippy Lints to Respect

2.4 Fix warnings, don’t silence them!

NEVER just #[allow(clippy::lint_something)] unless:

• You truly understand why the warning happens and you have a reason why it is better that way.
• You document why it is being ignored.
• ❗ Don’t use allow, but expect, it will give a warning in case the lint is not true anymore, #[expect(clippy::lint_something)].

Example:

The fix would be:

rustCopy

// Faster matching is preferred over size efficiency
#[expect(clippy::large_enum_variant)]
enum Message {
    Code(u8),
    Content(Box<[u8; 1024]>),
}

Handling false positives

Sometimes Clippy complains even when your code is correct, in those cases there are two solutions:

1. Try to refactor the code, so it improves the warning.
2. Locally override the lint with #[expect(clippy::lint_name)] and a comment with the reason.
3. Avoid global overrides, unless it is core crate issue, a good example of this is the Bevy Engine that has a set of lints that should be allowed by default.

2.5 Configure workspace/package lints

In your Cargo.toml file it is possible to determine which lints and their priorities over each other. In case of 2 or more conflicting lints, the higher priority one will be chosen. Example configuration for a package:

And for a workspace: