-
Notifications
You must be signed in to change notification settings - Fork 43
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
chore: clippy fixes #728
base: main
Are you sure you want to change the base?
chore: clippy fixes #728
Conversation
df523d0
to
035ea9c
Compare
One other thing to note. Currently it should fail when run for the first time. The reason is that the latest commit to main added two methods which return a result, but will never return an error. I kept it in partly as a check that CI should fail the first time and unlike the initial batch of changes it is an API change to remove the Result. |
The CI failed as expected an I disabled |
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 for this cleanup. This looks good to me for the most part, besides a couple questionable diagnostics/changes I've pointed in comments.
The change looks good to me - I think we can merge it when the fmt check is passed and the remaining few failures are resolved. |
CI fails with I'm not sure I understand how to fix it, but I suppose the reason has something to do with the newly introduced |
@dmkozh fixed it. Was an ENV VAR for cargo home, which was from a previous attempt to have the clippy lints in a file. |
Seems like there are some failures in guest library. |
@dmkozh I also seem to get the following error if I ran that command locally:
I get:
|
That's likely because you're missing |
Hey @willemneal sorry for the delay (and inevitable bitrot). I've merged a run of |
What
Add a clippy check to CI and make initial pass at fixing clippy errors.
At first the number of lints was way too high to tackle all at once. However, disabling some that could be debatable allowed a lot of the obvious fixes to be done.
In future PRs the disabled lints can be addressed in batches to ensure so that it's not too overwhelming.
Why
Currently the only repo that requires that clippy is the CLI and this repo seems more important to have standard coding practices. Clippy can even help catch some logic errors.
Known limitations
[TODO or N/A]