[swift-evolution] [Proposal] Sealed classes by default
davesweeris at mac.com
Wed Jun 29 12:21:04 CDT 2016
> On Jun 29, 2016, at 12:15 PM, Michael Peternell <michael.peternell at gmx.at> wrote:
>> Am 29.06.2016 um 15:54 schrieb David Sweeris via swift-evolution <swift-evolution at swift.org>:
>> +1 for the concept of a "sealed” class.
>> -1 for making it default.
> Aren't sealed classes already implemented? I think the keyword is `final`..
> So there is nothing left to do :)
No, `final` doesn’t allow for any subclassing, but `sealed` allows for subclassing within your module (where you can presumably write more efficient code based on knowledge of each subclass).
- Dave Sweeris
More information about the swift-evolution