Email me

Clippy lints / Suspicious

Clippy lint · Suspicious · checked with Clippy 0.1.99

clippy::blanket_clippy_restriction_lints: `clippy::restriction` is not meant to be enabled as a group

What it meansChecks for warn/deny/forbid attributes targeting the whole clippy::restriction category. It is in the suspicious group and warns by default.

What you see

warning: `clippy::restriction` is not meant to be enabled as a group
 --> main.rs:1:9
  |
1 | #![deny(clippy::restriction)]
  |         ^^^^^^^^^^^^^^^^^^^
  |
  = help: enable the restriction lints you need individually
  = help: for further information visit https://rust-lang.github.io/rust-clippy/stable/index.html#blanket_clippy_restriction_lints
  = note: `#[warn(clippy::blanket_clippy_restriction_lints)]` 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?

Restriction lints sometimes are in contrast with other lints or even go against idiomatic rust. These lints should only be enabled on a lint-by-lint basis and with careful consideration.

Code that is most likely wrong or useless. Warns by default.

How to fix it

Clippy does not fix this one automatically. Change the code by hand:

Flagged

#![deny(clippy::restriction)]

Write this instead

#![deny(clippy::as_conversions)]

Turn it off, or on

Allow it where it does not fit your code, as narrowly as you can:

On one item

#[allow(clippy::blanket_clippy_restriction_lints)]
fn my_function() { /* ... */ }

Whole crate (Cargo.toml)

[lints.clippy]
blanket_clippy_restriction_lints = "allow"

One run

cargo clippy -- -A clippy::blanket-clippy-restriction-lints

The [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.

Suspiciousgroup
warndefault level
nofixed by cargo clippy --fix
1.47.0added in Rust

Clippy's own documentation

What it does

Checks for warn/deny/forbid attributes targeting the whole clippy::restriction category.

Why is this bad?

Restriction lints sometimes are in contrast with other lints or even go against idiomatic rust. These lints should only be enabled on a lint-by-lint basis and with careful consideration.

Example

#![deny(clippy::restriction)]

Use instead:

#![deny(clippy::as_conversions)]

From the Clippy lint list (0.1.99), part of the Rust project, MIT or Apache-2.0. Official entry.

Related lints

All 847 Clippy lints · Rust compiler errors · Cargo.toml checker

Up next

Related lintclippy::await_holding_invalid_typeAllows users to configure types which should not be held across await suspension pointsRead it next →

Did this answer your question?

Get the receipts by email.

What my AI agents tried this week, with the real numbers: what worked, what flopped, what made money. One email when there is something worth reading.

No spam, never sold. Every email has a one-click unsubscribe.

Popular in the shop

All 124 tools →

Browse: Bundles and kitsHome, family and schoolMoney and businessAI toolsSports and fitnessMaking and hobbiesFood and drinkIndie dev and launchTrading and quant

Free: Landing page teardown iPhone app cost calculator LLM API cost calculator Paid online: $49 Launch Check App builds Articles FAQ