-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Fix approx_const for some new cases
#15236
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
Conversation
|
Lintcheck changes for 093b6e5
This comment will be updated if you push new changes |
|
Seems that triagebot isn't assigning me any issues. (Because I'm not the last one to touch any files). |
blyxyas
left a comment
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.
Great starting patch! I have some comments but things are looking great!
|
Thanks for the feedback! Just addressed the comments @rustbot ready |
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.
LGTM, thanks!
Could you squash these commits into one?
@rustbot author
|
Reminder, once the PR becomes ready for a review, use |
Improved naming and comment
|
Thank you for the review! Just squashed @rustbot ready |
Fix some cases for
approx_const:0s or using_) the lint now finds those caseschangelog: [
approx_const]: Fix when used over overly precise literals and non trivially formatted numeralsFixes #15194