-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
trait_duplication_in_bounds lint has misleading message #9151
Labels
C-bug
Category: Clippy is not doing the correct thing
Comments
aldhsu
changed the title
trait_duplication_in_bounds lint doesn't consider generics
trait_duplication_in_bounds lint has misleading message
Jul 11, 2022
aldhsu
added a commit
to aldhsu/rust-clippy
that referenced
this issue
Jul 12, 2022
- only compare where predicates to trait bounds when generating where clause specific message to fix rust-lang#9151 - use comparable_trait_ref to account for trait bound generics to fix rust-lang#8757
aldhsu
added a commit
to aldhsu/rust-clippy
that referenced
this issue
Jul 13, 2022
- only compare where predicates to trait bounds when generating where clause specific message to fix rust-lang#9151 - use comparable_trait_ref to account for trait bound generics to fix rust-lang#8757
aldhsu
added a commit
to aldhsu/rust-clippy
that referenced
this issue
Jul 13, 2022
- only compare where predicates to trait bounds when generating where clause specific message to fix rust-lang#9151 - use comparable_trait_ref to account for trait bound generics to fix rust-lang#8757
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
TRAIT_DUPLICATION_IN_BOUNDS lint.
Trait duplications within bounds raises a lint that refers to where clauses that don't exist.
Reproducer
I tried this code:
I expected to see this happen:
The error message to warn about trait duplication within bounds or alternatively no error.
Instead, this happened:
Error refers to a where clause that doesn't exist.
Version
Additional Labels
No response
The text was updated successfully, but these errors were encountered: