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

Matthew Johnson matthew at anandabits.com
Wed Dec 23 20:46:17 CST 2015

> On Dec 23, 2015, at 8:43 PM, Charles Srstka <cocoadev at charlessoft.com> wrote:
>> On Dec 23, 2015, at 8:15 PM, Matthew Johnson via swift-evolution <swift-evolution at swift.org <mailto:swift-evolution at swift.org>> wrote:
>> I’m not trying to force my opinion on anyone.  I’m just making a case for the advantages of a particular default.  Changing the default does not break inheritance at all.  Nobody has to use the default when it doesn’t fit the design they wish to implement.  
> I disagree; changing the default will largely break inheritance, because hardly anything (in pure-Swift frameworks; I know that Obj-C will still be what it is) will be overridable anymore, unless the framework author specifically anticipated your use case. Which when we’re dealing with human developers, isn’t necessarily going to be the case.

Please read the post I just sent regarding 3rd party frameworks and libraries and comment there if you disagree.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20151223/a1fc28ec/attachment.html>

More information about the swift-evolution mailing list