Clippy lints / Complexity
Clippy lint · Complexity · checked with Clippy 0.1.99
clippy::zero_divided_by_zero: constant division of `0.0` with `0.0` will always result in NaN
What it meansChecks for 0.0 / 0.0. It is in the complexity group and warns by default.
What you see
warning: constant division of `0.0` with `0.0` will always result in NaN --> main.rs:3:11 | 3 | let nan = 0.0f32 / 0.0; | ^^^^^^^^^^^^ | = help: consider using `f32::NAN` if you would like a constant representing NaN = help: for further information visit https://rust-lang.github.io/rust-clippy/stable/index.html#zero_divided_by_zero = note: `#[warn(clippy::zero_divided_by_zero)]` 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?
It’s less readable than f32::NAN or f64::NAN.
Code that does something simple in a complicated way. Warns by default.
How to fix it
Clippy does not fix this one automatically. Change the code by hand:
Flagged
let nan = 0.0f32 / 0.0;
Write this instead
let nan = f32::NAN;
Turn it off, or on
Allow it where it does not fit your code, as narrowly as you can:
On one item
#[allow(clippy::zero_divided_by_zero)]
fn my_function() { /* ... */ }Whole crate (Cargo.toml)
[lints.clippy]
zero_divided_by_zero = "allow"One run
cargo clippy -- -A clippy::zero-divided-by-zeroThe [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 0.0 / 0.0.
Why is this bad?
It’s less readable than f32::NAN or f64::NAN.
Example
let nan = 0.0f32 / 0.0;
Use instead:
let nan = f32::NAN;
From the Clippy lint list (0.1.99), part of the Rust project, MIT or Apache-2.0. Official entry.
Related lints
- too_many_argumentsChecks for functions with too many parameters
- clone_on_copyusing `clone` on type `u64` which implements the `Copy` trait
- type_complexityChecks for types used in structs, parameters and let declarations above a certain complexity threshold
- vec_box`Vec<T>` is already on the heap, the boxing is unnecessary
- while_let_loopthis loop could be written as a `while let` loop
- wildcard_in_or_patternsChecks for wildcard pattern used with others patterns in same match arm
- zero_prefixed_literalthis is a decimal constant
All 847 Clippy lints · Rust compiler errors · Cargo.toml checker
Up next
Related lintclippy::too_many_argumentsChecks for functions with too many parametersRead it next →Did this answer your question?