Make it crystal clear what lint `type_alias_bounds` actually signifies#126575

Merged

bors merged 9 commits intorust-lang:masterfrom

fmease:update-lint-type_alias_bounds

Jul 26, 2024

Commits on Jul 22, 2024

Suggesting an available assoc item is always maybe-incorrect
fmease
committed
HIR ty lowering: Refactor the way the projectee ("QSelf") gets passed to diagnostics
fmease
committed
Inside eager ty aliases on unresolved assoc tys suggest fully qualifying instead of restricting their self ty
fmease
committed
Suggest full trait ref (with placeholders) on unresolved assoc tys
fmease
committed
Don't suppress lint type_alias_bounds for ty aliases containing inherent assoc tys
fmease
committed
Suppress lint type_alias_bounds for ty aliases containing const projections under GCE
fmease
committed
Improve the impl and diag output of lint type_alias_bounds
fmease
committed
Make lint type_alias_bounds's removal sugg maybe-incorrect if the RHS contains shorthand assoc tys
fmease
committed
Update the description of lint type_alias_bounds
fmease
committed