<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><br><br>Sent from my iPhone</div><div><br>On Dec 23, 2015, at 2:28 PM, Felipe Cypriano via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br><br></div><blockquote type="cite"><div>
<title></title>
<div>On Wed, Dec 23, 2015, at 11:12, Felipe Cypriano wrote:<br></div>
<blockquote type="cite"><div>About sealed vs final. I think this is a do or do not, sealed would just<br></div>
<div>complicate things by having different behavior depending on where the<br></div>
<div>code is. I'd go with final by default or not go at all.<br></div>
</blockquote><div> </div>
<div>I changed my mind about sealed being a bad thing, this email from [John McCall](<a href="https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20151207/001032.html">https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20151207/001032.html</a>) has very good points.<br></div>
<div> </div>
<div>---<br></div>
<div> </div>
<div>Also I just noticed that this thread title mentions methods as final by default, but I can't find an example/proposal of how it would work. My question is is anyone suggesting that methods must be marked as "overridable" even if the class is inheritable? E.g:<br></div></div></blockquote><div><br></div>The original post did indeed have that intention. However, pretty much the entire thread has been focused exclusively on classes, not methods. That has turned out to be a plenty big can of worms on its own.<div><br></div><div>I think it's best to keep this thread focused on classes. We can start a new thread for methods later if desired. But we should wait until the dust has settled on the classes conversation IMO.</div><div><br></div><div><br><blockquote type="cite"><div>
<div> </div>
<div>```<br></div>
<div>open class Money {<br></div>
<div> func vanish() {<br></div>
<div> }</div>
<div>}</div>
<div>```<br></div>
<div> </div>
<div>Is `vanish` final?<br></div>
<div> </div>
<img src="https://u2002410.ct.sendgrid.net/wf/open?upn=eLFMrKDT8iBxZ-2Fbnk-2BZqvSchNN-2FvYXdceA0T7VxwkAdF0fZBB0erTap-2Bs8fqCa4yrkLte8gTa3unxFnmnMiH3V7YqfWldZzrR9-2B8lY7RFlx1Q3aApsGxV-2B80Nvoi9szggCWPSFT1IoyCMdjhdq7Tv5HVq007VG-2B3lQ1JXdSct0JbjbG52Z8IE62I8PG2-2Fbxyvic1QEPyNQkB814Q0758J50J-2F6fuVltp3nrbT6AgPFQ-3D" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;">
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>swift-evolution mailing list</span><br><span><a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a></span><br><span><a href="https://lists.swift.org/mailman/listinfo/swift-evolution">https://lists.swift.org/mailman/listinfo/swift-evolution</a></span><br></div></blockquote></div></body></html>