You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had the following f32 literal: 0.000110694319115641.
Clippy recommends truncating it to 0.000_110_694_32. So far, so good.
After I replace it, and run cargo clippy again, I'm facing the following output:
43 | 0.000_110_694_32,
| ^^^^^^^^^^^^^^^^ help: did you mean to write: `0.000_110_694_f32`
I understand the idea behind the mistyped suffix check and I know I can make it go away by adding #[allow(clippy::mistyped_literal_suffixes)] but it would be nice if clippy didn't recommend something it would fail on the next time.
The text was updated successfully, but these errors were encountered:
I had the following f32 literal:
0.000110694319115641
.Clippy recommends truncating it to
0.000_110_694_32
. So far, so good.After I replace it, and run
cargo clippy
again, I'm facing the following output:I understand the idea behind the mistyped suffix check and I know I can make it go away by adding
#[allow(clippy::mistyped_literal_suffixes)]
but it would be nice if clippy didn't recommend something it would fail on the next time.The text was updated successfully, but these errors were encountered: