3 weeks to delegation! Please help

[elahn]

It's a good summary of what needs to be addressed. Why the RFC stalled isn't important right now, but some of the reasons can be inferred from this.

I completely agree with @Ixrec about attribute syntax:

@Ixrec

Various attribute syntaxes like #[delegate(foo=S)]. Most of these made it hard to tell what was the item being delegated and what was the field being delegated to. This also seems like it would lead to “stringly typed” attribute syntax like #[delegate(foo="self.f.foo()")] if we tried to make it cover most of the possible future extensions. Also, attributes for an impl block would normally go outside the impl block, but since delegation is purely an implementation detail it again seems strange to put it outside the block. Finally, an attribute would be appropriate if this feature could be implemented as a proc macro someday, but delegation cannot because it requires “looking outside” the impl block to see all the items in the trait being implemented.

Anything you have time to contribute, even comments here would be appreciated. Nothing is off the table, but I like @Ixrec's approach of a simple base feature and everything else as possible extensions. Nonetheless, we should make sure the base feature is forward compatible with possible extensions, so suggest away!