<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 21, 2015, at 2:03 PM, Tino Heth via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br><br></div><blockquote type="cite"><div><meta http-equiv="Content-Type" content="text/html charset=utf-8"><div><br class=""><blockquote type="cite" class=""><div class=""><div class="" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">- 'private' and 'internal' methods are not exposed outside of a library, so you can't call them, much less override them. Similar for 'private' and 'internal' classes: you cannot subclass them.</div></div></blockquote></div>really important point — and imho one of the best arguments not to make final the default:<div class="">It IS already the default (practically), so all points regarding own frameworks used by other parties become much less relevant.</div>
<img src="https://u2002410.ct.sendgrid.net/wf/open?upn=eLFMrKDT8iBxZ-2Fbnk-2BZqvSchNN-2FvYXdceA0T7VxwkAfLOreEst6tZeDQ3STSIB9kaoyOepRvmB-2BqdUOwKIPzAxKcnqy6Cc7CYsMNSspHFkyGFQIL2uKXl2-2Bf8CBhMgIZLNFBQjNInpyY0gvxlvMkwVkpKeJudD1EJkdiVdKwimlkwL-2Ft0ejBLzCc6YdtdIx09n13KvoJjPgLaZ7nrx3j3p9s0HpU7nMb0uyeW04TiPo-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><div><br></div><div>This is not true at all. You are making the case that 'sealed' is "practically" the default, not 'final'.</div><div><br></div><div>I can see why you view it this way, but access control and inheritability are orthogonal. A framework class that needs to be publicly visible does not necessarily need to be inheritable and there are compelling reasons why that should not be allowed by default.</div><div><br></div><div><br></div><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></body></html>