-
-
Notifications
You must be signed in to change notification settings - Fork 3.9k
[Merged by Bors] - fix clippy
warning failing on CI
#2353
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
[Merged by Bors] - fix clippy
warning failing on CI
#2353
Conversation
This popped up on my recent push to #2332 |
Now I'm especially consufed. |
@mockersf any ideas? |
Running clippy with:
Fixes that Problem. To me this seems like a Bug in Clippy. |
Darn :/ |
It's rust-lang/rust-clippy#7290 The workaround proposed there works: add |
clippy::bool-assert-comparison
warning failing on CIclippy
warning failing on CI
Looks good to me. Nice work! |
bors r+ |
# Objective - CI jobs are starting to fail due to `clippy::bool-assert-comparison` and `clippy::single_component_path_imports` being triggered. ## Solution - Fix all uses where `asset_eq!(<condition>, <bool>)` could be replace by `assert!` - Move the `#[allow()]` for `single_component_path_imports` to `#![allow()]` at the start of the files.
Pull request successfully merged into main. Build succeeded: |
clippy
warning failing on CIclippy
warning failing on CI
# Objective - CI jobs are starting to fail due to `clippy::bool-assert-comparison` and `clippy::single_component_path_imports` being triggered. ## Solution - Fix all uses where `asset_eq!(<condition>, <bool>)` could be replace by `assert!` - Move the `#[allow()]` for `single_component_path_imports` to `#![allow()]` at the start of the files.
Objective
clippy::bool-assert-comparison
andclippy::single_component_path_imports
being triggered.Solution
asset_eq!(<condition>, <bool>)
could be replace byassert!
#[allow()]
forsingle_component_path_imports
to#![allow()]
at the start of the files.