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

Craig Cruden ccruden at novafore.com
Wed Dec 23 12:43:46 CST 2015

I thought sealed and final were effectively the same thing for production code, which is why it confuses me when you say final is right anything less including sealed is not.

In Scala at least sealed is final with the exception that subclasses within the same source file are allowed.  When it is compiled and shipped - you can no longer modify that source file….. 

> On 2015-12-24, at 1:36:01, Matthew Johnson via swift-evolution <swift-evolution at swift.org> wrote:
> I strongly feel that I shouldn’t pay a price in production code in order to better support those use cases.  IMO ‘final’ is the right default for production code and we pay a price if the default is anything less, including ‘sealed’. 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20151224/80076f66/attachment.html>

More information about the swift-evolution mailing list