-
Notifications
You must be signed in to change notification settings - Fork 4
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
Clippy Cleanup II #779
base: main
Are you sure you want to change the base?
Clippy Cleanup II #779
Conversation
why is it better to not use return? |
To prevent merge conflicts, can you revert the changes made related to confusion & drunk aura, I'm going to make the same or equivalent changes in red herrings. |
I'll put a comment on each file with a change. |
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.
Here
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.
here
Its just those 2 |
I don't know how to review this I need clippy on my computer first to review this |
This reverts commit 9e8b585.
I fucked up the merge, and then reverted it but github still thinks its merged. How do I fix it? |
think I fixed it
fr this time
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.
Server tests fail
Also help me get clippy on my machine :P
This doesn't touch cop or ambusher, waiting til #764 is merged
This fixes warnings from the 'clippy' linter (the best linter) in preparation for @ItsSammyM getting his laptop set back up -- this way the transition to adding cargo clippy to his computer is not filled with yellow underlines.
If this is merged and Sam installs clippy, I might change the build action to check for clippy warnings too