You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
which generates a impl<T: Foo> Foo for Impl<T> and a useless, incorrect impl Foo for () which panics.
(assuming you want an implementation for a type that isn't(), but the type you want lives in a downstream crate.)
Maybe this can be referred to as delegating implementation.
The core of the issue seems to be that it appears ridiculous that you annotate a function, but that function ends up not being used. Instead we could just annotate the full trait:
audunhalland
changed the title
There is no way to just generate an implementation for Impl<T>, without also implementing for some T
Concrete mode: There is no way to just generate an implementation for Impl<T>, without also implementing for some T
Jul 7, 2022
This relates to the definition of dependency "leaf nodes".
The text was updated successfully, but these errors were encountered: