[swift-evolution] Final by default for classes and methods

Jordan Rose jordan_rose at apple.com
Mon Dec 21 13:26:39 CST 2015

> On Dec 20, 2015, at 3:40 , Tino Heth via swift-evolution <swift-evolution at swift.org> wrote:
>> Frankly, I think having `final` in the language at all is a mistake. While I agree that we should prefer composition to inheritance*, declaring things final is hubris. The only reasonable use case I've seen is for optimization, but that smacks of developers serving the compiler rather than the converse. Bringing an analog of NS_REQUIRES_SUPER to Swift would be most welcome; that's as far as I'd go down the path of dictating framework usage.
> I really like the direction this discussion has taken ;-):
> Is there any counter argument beside performance (which imho should always be seen under the aspect of premature optimization) that speaks against making NS_REQUIRES_SUPER the default behavior?

I personally don't like this but I can't put my finger on why. Obviously there are some things where you really don't need to call super (mostly abstract methods), but you just said "default", which implies that we could have an opt-out attribute.

I will say, however, that making NS_REQUIRES_SUPER the default for overridable methods is separable from deciding which methods are overridable by default. Making sure the base method is called isn't really the same as knowing the base method is all that's called.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20151221/3312b91c/attachment.html>

More information about the swift-evolution mailing list