Lint for unnecessary trait bounds #8366
Labels
A-lints
Area: Lints (warnings about flaws in source code) such as unused_mut.
C-enhancement
Category: An issue proposing an enhancement or a PR with one.
E-hard
Call for participation: Hard difficulty. Experience needed to fix: A lot.
It's easy to accidentally leave an unnecessary (e.g.)
Clone
bound when refactoring a function, making the function less generic/useful than it otherwise could be.This would warn for something like:
It would presumably have to be very careful about super-traits i.e. using a function from a super-trait, but not one from the listed trait bound, would either not warn at all, or suggest that the constraints could be weakened to that trait (handling multiple supertraits would be even trickier, i.e. if a function from 2 different super-traits was called, is it sensible/useful to suggest weakening to a combination of those two traits?)
Presumably a far-future feature, if at all.
The text was updated successfully, but these errors were encountered: