<div dir="ltr">Do we really need a new keyword? Since we already have syntax like `internal(set)` couldn't we do `internal(unsealed)`, etc.</div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jun 29, 2016 at 12:21 PM, David Sweeris via swift-evolution <span dir="ltr"><<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">> On Jun 29, 2016, at 12:15 PM, Michael Peternell <<a href="mailto:michael.peternell@gmx.at">michael.peternell@gmx.at</a>> wrote:<br>
><br>
><br>
>> Am 29.06.2016 um 15:54 schrieb David Sweeris via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>>:<br>
>><br>
>> +1 for the concept of a "sealed” class.<br>
>> -1 for making it default.<br>
><br>
> Aren't sealed classes already implemented? I think the keyword is `final`..<br>
> So there is nothing left to do :)<br>
<br>
</span>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).<br>
<br>
- Dave Sweeris<br>
<div class="HOEnZb"><div class="h5">_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
</div></div></blockquote></div><br></div>