Clippy lints / Restriction
Clippy lint · Restriction · checked with Clippy 0.1.99
clippy::question_mark_used: Checks for expressions that use the ? operator and rejects them
What it meansChecks for expressions that use the ? operator and rejects them. It is in the restriction group and off by default.
Does it matter?
Sometimes code wants to avoid the ? operator because for instance a local block requires a macro to re-throw errors to attach additional information to the error.
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
let result = expr?;
Write this instead
utility_macro!(expr);
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]
question_mark_used = "warn"In code
#![warn(clippy::question_mark_used)]One run
cargo clippy -- -W clippy::question-mark-usedThe [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 expressions that use the ? operator and rejects them.
Why restrict this?
Sometimes code wants to avoid the ? operator because for instance a local
block requires a macro to re-throw errors to attach additional information to the
error.
Example
let result = expr?;
Could be written:
utility_macro!(expr);
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
- pub_useusing `pub use`
- pub_with_shorthandusage of `pub` without `in`
- pub_without_shorthandusage of `pub` with `in`
- rc_bufferChecks for Rc<T> and Arc<T> when T is a mutable buffer type such as String or Vec
- rc_mutexChecks for Rc<Mutex<T>>
- redundant_test_prefixChecks for test functions (functions annotated with #[test]) that are prefixed with test_ which is redundant
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?