Clippy lints / Restriction
Clippy lint · Restriction · checked with Clippy 0.1.99
clippy::unimplemented: `unimplemented` should not be present in production code
What it meansChecks for usage of unimplemented!. It is in the restriction group and off by default.
What you see
warning: `unimplemented` should not be present in production code --> main.rs:3:1 | 3 | unimplemented!(); | ^^^^^^^^^^^^^^^^ | = help: for further information visit https://rust-lang.github.io/rust-clippy/stable/index.html#unimplemented = note: requested on the command line with `-W clippy::unimplemented`
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 macro, or panics in general, may be unwanted in production code.
Lints that forbid language features for specific codebases (no unwrap, no indexing...). Off by default; pick them one by one, never the whole group.
How to fix it
Clippy does not fix this one automatically. Change the code by hand:
Flagged
unimplemented!();
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]
unimplemented = "warn"In code
#![warn(clippy::unimplemented)]One run
cargo clippy -- -W clippy::unimplementedThe [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 usage of unimplemented!.
Why restrict this?
This macro, or panics in general, may be unwanted in production code.
Example
unimplemented!();
From the Clippy lint list (0.1.99), part of the Rust project, MIT or Apache-2.0. Official entry.
Related lints
- unwrap_usedChecks for .unwrap() or .unwrap_err() calls on Results and .unwrap() call on Options
- module_name_repetitionsDetects public item names that are prefixed or suffixed by the containing public module’s name
- expect_usedChecks for .expect() or .expect_err() calls on Results and .expect() call on Options
- todo`todo` should not be present in production code
- try_errreturning an `Err(_)` with the `?` operator
- undocumented_unsafe_blocksChecks for unsafe blocks and impls without a // SAFETY: comment explaining why the unsafe operations performed inside the block are safe. Note the comment must appear on the line(s) preceding the unsafe block with nothing appearing in between
- unnecessary_rest_patternunnecessary rest pattern (`..`)
- unnecessary_safety_commentstatement has unnecessary safety comment
- unnecessary_safety_docChecks for the doc comments of publicly visible safe functions and traits and warns if there is a # Safety section
All 847 Clippy lints · Rust compiler errors · Cargo.toml checker
Up next
Related lintclippy::unwrap_usedChecks for .unwrap() or .unwrap_err() calls on Results and .unwrap() call on OptionsRead it next →Did this answer your question?