[swift-evolution] [swift-evolution-announce] [Review #2] SE-0117: Default classes to be non-subclassable publicly
garth at garthsnyder.com
Sun Jul 17 14:14:46 CDT 2016
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.
More information about the swift-evolution