-
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
Port mitsuhiko's excessive bools lints #5125
Conversation
cb22824
to
d06fc2a
Compare
e310333
to
bead760
Compare
fixed, I think |
☔ The latest upstream changes (presumably #5061) made this pull request unmergeable. Please resolve the merge conflicts. |
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! Only 3 NITs and a rebase left to do.
2586037
to
3901ca7
Compare
3901ca7
to
338fb7a
Compare
@bors r+ |
📌 Commit 338fb7a has been approved by |
Port mitsuhiko's excessive bools lints Closes #4 . changelog: add `struct_excessive_bools` and `fn_params_excessive_bools` lints. I moved is_trait_impl_item check because at first I implemented it as a late pass for some reason but then I realized it's actually an early lint. But it's a useful function to have, should I move it into a separate pr?
💔 Test failed - checks-travis |
@bors retry |
Port mitsuhiko's excessive bools lints Closes #4 . changelog: add `struct_excessive_bools` and `fn_params_excessive_bools` lints. I moved is_trait_impl_item check because at first I implemented it as a late pass for some reason but then I realized it's actually an early lint. But it's a useful function to have, should I move it into a separate pr?
💔 Test failed - checks-travis |
@bors retry |
Port mitsuhiko's excessive bools lints Closes #4 . changelog: add `struct_excessive_bools` and `fn_params_excessive_bools` lints. I moved is_trait_impl_item check because at first I implemented it as a late pass for some reason but then I realized it's actually an early lint. But it's a useful function to have, should I move it into a separate pr?
☀️ Test successful - checks-travis, status-appveyor |
Closes #4 .
changelog: add
struct_excessive_bools
andfn_params_excessive_bools
lints.I moved is_trait_impl_item check because at first I implemented it as a late pass for some reason but then I realized it's actually an early lint. But it's a useful function to have, should I move it into a separate pr?