Skip to content
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

"Fix" clippy checks in CI, resolve a bunch of clippy warnings #1134

Merged
merged 8 commits into from
Feb 2, 2024

Conversation

jessebraham
Copy link
Member

This is a bit of a mess, but tl;dr our clippy checks in CI have been broken for some time, and this is a good first step to get things in a good state again.

There is still work to be done here, but I think I've got a bulk of the warnings silenced now. I still have a number of lints which I'm allowing for the time being, but I will eliminate these in time; I will be re-writing the workflow soon as part of our unification efforts anyway, so not a huge deal.

Left the ESP32-P4 disabled for now, just going to be too annoying to deal with until we've made some more progress there.

I've largely just blindly done what clippy told me to here, so if there's anything that looks wrong or especially strange please let me know!

@jessebraham
Copy link
Member Author

Oops, forgot to write some safety comments; will draft this until I resolve that 😅

@jessebraham jessebraham marked this pull request as draft February 1, 2024 18:01
@bjoernQ
Copy link
Contributor

bjoernQ commented Feb 2, 2024

Had a brief look at every change - looks good. Mostly changes things to the better but I don't really agree with Clippy everywhere but that's a me thing 👍

@jessebraham
Copy link
Member Author

Mostly changes things to the better but I don't really agree with Clippy everywhere but that's a me thing 👍

If there are any specific lints you think should be disabled we can do so, I'm just apprehensive to add exceptions as I imagine the list will just grow with time.

(I realize I'm allowing certain lints in this PR, but that's temporary because some of them require refactoring and I wanted to leave that for another PR)

@bjoernQ
Copy link
Contributor

bjoernQ commented Feb 2, 2024

Mostly changes things to the better but I don't really agree with Clippy everywhere but that's a me thing 👍

If there are any specific lints you think should be disabled we can do so, I'm just apprehensive to add exceptions as I imagine the list will just grow with time.

(I realize I'm allowing certain lints in this PR, but that's temporary because some of them require refactoring and I wanted to leave that for another PR)

It's really just minor things like in some places we have a #[cfg(any(one-item))] where we expect more in future ... but adding that any then is not a problem. We should only add exceptions for very good reasons ... this isn't a good enough reason 😄

@jessebraham jessebraham added the skip-changelog No changelog modification needed label Feb 2, 2024
@jessebraham jessebraham marked this pull request as ready for review February 2, 2024 15:27
@jessebraham
Copy link
Member Author

Should be good to go here now, I think.

Copy link
Contributor

@bjoernQ bjoernQ left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM - that wasn't fun I guess

@jessebraham jessebraham added this pull request to the merge queue Feb 2, 2024
Merged via the queue into esp-rs:main with commit 285cfe4 Feb 2, 2024
17 of 18 checks passed
@jessebraham jessebraham deleted the fixes/clippy branch February 2, 2024 16:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
skip-changelog No changelog modification needed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants