Join GitHub today
Lint: Multiple inherent impls #414
We may want to have a lint that checks for multiple inherent impls. Why those are not problematic from a language standpoint, they can split the implementation of a type and make the code harder to navigate.
The hardest part is that the lint needs some storage, namely a set of type names that already had inherent impls, but we already have examples of that.
changed the title from
Multiple inherent impls?
Lint: Multiple inherent impls
Oct 25, 2015
referenced this issue
May 29, 2018
I do agree that this should apply if the impls are in the same file; it makes the most sense to me to replace impl bounds with