[swift-evolution] [swift-evolution-announce] [Review #2] SE-0117: Default classes to be non-subclassable publicly

L. Mihalkovic laurent.mihalkovic at gmail.com
Sun Jul 17 22:57:06 CDT 2016

(From mobile)

> On Jul 17, 2016, at 9:14 PM, Garth Snyder via swift-evolution <swift-evolution at swift.org> wrote:
> Is there a summary somewhere of the motivation for allowing methods to be declared non-overridable within open classes?
> I’m not asking about any particular syntax or default, just why you'd want this facility at all. The proposal doesn’t mention this, and the discussion of the initial version never really seemed to reach the issue, either.
> I can see that there’s a potential for static dispatch on non-overridable methods when called from outside the module. But presumably there’s an architectural argument in favor of this restriction as well.

Because 1) someone woke up one morning and thought it would be great 2) it goes into the direction of making swift a language for non programmers 3) the core team wants it

> Garth
> _______________________________________________
> 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