On Dec 29, 2015, at 5:38 PM, Matthew Johnson <matt...@anandabits.com> wrote: > > >> On Dec 29, 2015, at 5:25 PM, Charles Srstka <cocoa...@charlessoft.com >> <mailto:cocoa...@charlessoft.com>> wrote: >> >> Strong +1 on this proposal. I use Objective-C’s forwarding mechanisms quite >> often in my custom view code, in order to separate the code managing the >> outer view, the layout of subviews within the view, and business logic into >> separate classes, all while presenting a single, monolithic interface to the >> user. The loss of this ability without writing tons of boilerplate is one of >> the things about Swift that makes me sad. >> >> The one thing I’d change is upgrading the partial forwarding synthesis to >> the original proposal, as that’s a rather important feature IMO. >> > > Thanks Charles. Do you disagree with the reasons I decided not to include > partial forwarding in the initial proposal (it is discussed in alternatives > considered)?
I see it in Future Enhancements, but not in Alternatives Considered (unless I’m just missing it). However, my thinking is that this isn’t really that hard to implement; just have the forwarding mechanism forward only methods that aren’t already implemented in the class. This would be similar to the way protocol extensions work, where if you implement the method you get that, but if you don’t implement it, you get the protocol extension’s implementation. Charles
_______________________________________________ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution
