-
Notifications
You must be signed in to change notification settings - Fork 293
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
Cleanup some clippy lints #454
Conversation
d8f83ab
to
713b550
Compare
Go for it!
I don't know of any way to quickly judge whether a PR introduces merge conflicts with other PRs. Before merging big PRs, I usually scan through the list of other PRs and see if there's any low-hanging fruit ready to be merged. I'm currently on my honeymoon and COVID's made my work weird (I do education research), so I'm short on time. If you have the desire and time to knock down the list of pending PRs, feel free to go for it! |
Hey, congratulations! Nice to hear this - I hope you're having a great time.
Wish you all the best for your work. |
713b550
to
9df0fa8
Compare
Bump. |
We already use is_empty in other places, so it is presumably consistent with these.
9df0fa8
to
0814544
Compare
I have now :) The bool matching change looks good; there's one tiny thing I've noticed but I think this can be merged. |
0814544
to
8a562f8
Compare
This looks good to me. Ready to merge, @phimuemue? |
bors r+ |
Build succeeded: |
I cleaned up some things I got from clippy. I only changed what I'd consider straightforward.
I think it would eventually be beneficial to resolve the remaining lints, so that it is easier to identify real problems spotted by clippy. Do we have a policy regarding this?
Off-topic: I would have merged this right away, but I did not want to introduce conflicts with existing PRs. Is there a way to check if my commits would introduce conflicts?