Clippy lints / Restriction
Clippy lint · Restriction · checked with Clippy 0.1.99
clippy::float_arithmetic: Checks for float arithmetic
What it meansChecks for float arithmetic. It is in the restriction group and off by default.
Does it matter?
For some embedded systems or kernel development, it can be useful to rule out floating-point numbers.
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
a + 1.0;
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]
float_arithmetic = "warn"In code
#![warn(clippy::float_arithmetic)]One run
cargo clippy -- -W clippy::float-arithmeticThe [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 float arithmetic.
Why restrict this?
For some embedded systems or kernel development, it can be useful to rule out floating-point numbers.
Example
a + 1.0;
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
- field_scoped_visibility_modifiersscoped visibility modifier on a field
- filetype_is_fileChecks for FileType::is_file()
- float_cmp_conststrict comparison of `f32` or `f64` constant
- fn_to_numeric_cast_anycasting function pointer `fn1` to `usize`
- get_unwrapcalled `.get().unwrap()` on a Vec
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?