Fix type_repetition_in_bounds

[Jarcho]

fixes #7360
fixes #8162
fixes #8056

changelog: Check for full equality in type_repetition_in_bounds rather than just equal hashes

[rust-highfive]

r? @llogiq

(rust-highfive has picked a reviewer for you, use r? to override)

[llogiq]

Great! More false positives quashed. Thank you! @bors r+

[bors]

📌 Commit 2dd216a has been approved by llogiq

[bors]

⌛ Testing commit 2dd216a with merge 20f2a89...

[bors]

☀️ Test successful - checks-action_dev_test, checks-action_remark_test, checks-action_test
Approved by: llogiq
Pushing 20f2a89 to master...

[jendrikw]

I think there is still a false positive in this case (or is the playground not using the latest version?):

playground

#![warn(clippy::type_repetition_in_bounds)]
fn f<I, J>(_: I, _: J)
where
    I: IntoIterator,
    <I as IntoIterator>::IntoIter: Clone,
    J: IntoIterator,
    <J as IntoIterator>::IntoIter: Clone,
{}

results in:

warning: this type has already been used as a bound predicate
 --> src/lib.rs:7:5
  |
7 |     <J as IntoIterator>::IntoIter: Clone,
  |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  |
note: the lint level is defined here
 --> src/lib.rs:1:9
  |
1 | #![warn(clippy::type_repetition_in_bounds)]
  |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  = help: consider combining the bounds: `<J as IntoIterator>::IntoIter: Clone + Clone`

[Jarcho]

Changes in clippy are only synced every two(?) weeks with the main repo. So it can take a little while for changes to make it to the playground.