Yes, it does, but I think it's an unnecessary overburdening of delegation functionality. Also this approach has several minor issues compared to one outlined in the inherent traits RFC:
- If all type functionality is expressed purely through traits it requires to add dummy
impl
block. - More typing and reading, compare
#[inherent]
line orinherent impl
withdelegate * to trait TraitOne;
(plus potential dummyimpl
block) - I am not sure if we need an ability to "delegate" hand picked methods from traits.
- How this delegation will look in rustdoc? With inherent traits the only change can be just a separate category "Inherent Trait Implementations", instead of duplicating methods.
- It's a "possible future extension", while in my opinion this feature can have a much bigger impact on ecosystem compared to the delegation (a lot of traits impls can be made inherent to improve ergonomics), so I think it should not be offloaded like that.