[swift-evolution] [swift-evolution-announce] [Review] SE-0026 Abstract classes and methods

Goffredo Marocchi panajev at gmail.com
Tue Mar 1 08:23:47 CST 2016

I really dislike the fact that default methods implemented in a protocol extension are statically dispatched by default... An optimisation which can have confusing side effects should be programmer driven not automagically applied, but we are going off topic I guess ;).

Sent from my iPhone

> On 1 Mar 2016, at 12:13, Gwendal Roué via swift-evolution <swift-evolution at swift.org> wrote:
>>> Le 1 mars 2016 à 11:29, Brent Royal-Gordon via swift-evolution <swift-evolution at swift.org> a écrit :
>>> I'm missing an important feature in your list: being able to declare protocol members with access scopes different from that of the protocol, i.e. private or internal in a public protocol.
>> Extension methods can always have different access control scopes from the protocol as a whole. The required/abstract methods are a different story, but I'll get into that later.
> Don’t you go too fast? Methods declared in protocol extensions are very different from methods declared inside the protocol: they are not dynamically dispatched.
> I, too, am concerned about the flat world of protocols' access control.
> Gwendal
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution

More information about the swift-evolution mailing list