I'm not seeing any real reason for (for example) HopSlotMap to have a Key bound on the generic K. This is against the general Rust style guide as it leads to infectious where clauses, and prevents being generic over it in more permissive GATs without awkward workarounds.
I'm not seeing any real reason for (for example) HopSlotMap to have a
Keybound on the genericK. This is against the general Rust style guide as it leads to infectiouswhereclauses, and prevents being generic over it in more permissive GATs without awkward workarounds.