-
Notifications
You must be signed in to change notification settings - Fork 236
ensure clippy runs on all targets #262
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
ensure clippy runs on all targets #262
Conversation
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.
Can you please split the commits so that we have only one commit per type of change?
d228e99
to
7fc90e9
Compare
1f820ff
to
4575e9b
Compare
note that there is some remaining use of deprecated code in the examples. It's not clear to me how these use cases should be supported using the builder API. I've allowed these for now, but they should be addressed in a future PR |
f9bb99d
to
2aeffe3
Compare
For the "global" example you can cherry-pick matthiasbeyer@1eff7b3 to this PR if you want (or wait until the actions succeed) 😆 |
this change doesn't look equivalent to the original to me. If i'm reading it right, the original example is mutable global config, while the updated version is immutable global config. in any case, I think I'd rather leave it out of this PR. Don't want to over-complicate the review! |
Okay! |
2aeffe3
to
a880573
Compare
Do you consider this review/merge ready? 😄 I think I lost track a bit! |
yes, i'm not planning to do any more on this PR |
note that there are clippy false positives due to rust-lang/rust-clippy#8140