-
Notifications
You must be signed in to change notification settings - Fork 13
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: fix some Clippy lints #1068
Conversation
Ready for review. This PR fixes easy and non-ambiguous lints. Remaining unfixed lints include:
More PRs to follow for the remaining ones. |
Thank you!
If you want to address this one, let me know beforehand so we can discuss on how it should be approached.
Actually, it’s probably a sign that the
For that one, in order of preference, I recommend:
That being said, those are just guidelines, and anything is acceptable :) |
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.
This lint became a hard error in [1.80.0](https://github.com/rust-lang/rust/releases/tag/1.80.0).
All `context()` messages checked and fixed.
I reworded a bit your individual commits so we can merge rebase them without squashing everything. It mostly comes down to the fact that changing code without modifying the semantic is a "refactor", changes to doc only (including comments) should be "docs" and I added the scope when it made sense. It’s mostly relevant for features and bug fixes that are actually perceived by the end user as we have scripts looking for these commits when generating the changelog to avoid forgetting important changes. This is based on the conventional commit specification. All that said, I should document the details and how we are using it in the repository directly :) |
No description provided.