-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move check for lossy whole-number floats out of excessive_precision
#5202
Move check for lossy whole-number floats out of excessive_precision
#5202
Conversation
f2a486b
to
c25f1ea
Compare
c25f1ea
to
219c94d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
@bors r+ |
📌 Commit 219c94d has been approved by |
…literal-restriction, r=flip1995 Move check for lossy whole-number floats out of `excessive_precision` changelog: Add new lint `lossy_float_literal` to detect lossy whole number float literals and move it out of `excessive_precision` again. Fixes #5201
💔 Test failed - checks-action_test |
@bors retry |
…literal-restriction, r=flip1995 Move check for lossy whole-number floats out of `excessive_precision` changelog: Add new lint `lossy_float_literal` to detect lossy whole number float literals and move it out of `excessive_precision` again. Fixes #5201
💔 Test failed - checks-action_test |
@bors retry (MacOS toolchain download...) |
☀️ Test successful - checks-action_dev_test, checks-action_remark_test, checks-action_test |
changelog: Add new lint
lossy_float_literal
to detect lossy whole number float literals and move it out ofexcessive_precision
again.Fixes #5201