[swift-evolution] Static Dispatch Pitfalls
panajev at gmail.com
Sat May 21 07:39:55 CDT 2016
Adding code to what really always sounded to me like pure interfaces/API contracts decoupling functionality from concrete implementation does bring its fair share of headaches, but in your experience is it really something delivering big upsides?
I do agree that in both Swift and Java the code in protocols/interfaces ship has long sailed so it is a moot point.
Sent from my iPhone
On 21 May 2016, at 13:25, Brent Royal-Gordon via swift-evolution <swift-evolution at swift.org> wrote:
>> Making them final is not a good idea. I see the default implementations in protocols as something that should replace the optional methods in @objc protocols.
> We aren't discussing default implementations. We're discussing methods that are listed *only* in the protocol extension, not in the protocol itself. These methods cannot be "overridden" in the way that a defaulted protocol method can be; I think it's safest to outlaw any attempt to "override" them at all.
> Brent Royal-Gordon
> swift-evolution mailing list
> swift-evolution at swift.org
More information about the swift-evolution