-
Notifications
You must be signed in to change notification settings - Fork 97
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 in Regressions. #1403
Clippy in Regressions. #1403
Conversation
…/kani into yoshi-clippy-compliance
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.
I'm not sure how clippy gets configured for a whole workspace, so I'm not sure if the first comment has a solution, the second one should probably be "fixed" before merging
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 doing this. I have 2 questions:
- Is there a reason why you preferred
.cargo/config.toml
instead ofclippy.toml
. - How long does
cargo clippy
takes? I was wondering if we should enable this in our regression.
I don't think that is possible, and keeping it so seems to be the stance from clippy devs: rust-lang/rust-clippy#1313 (comment). The idea behind it seems to be that you would control all lints at once, not just clippy lints.
It takes no longer than 2 compiles with |
LGTM ✅ |
Description of changes:
No change to kani behavior. Added
clippy
linter to regression suite.Resolved issues:
Lack of clippy lint checking in kani regression script. #1373 will stay open to track actual clippy errors.
Call-outs:
The current setup addresses the following clippy regressions.
Testing:
How is this change tested? Run the regression script
Is this a refactor change?
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.