+1 on both comments.<br><br>--<br>Ilya Belenkiy<br><div class="gmail_quote"><div dir="ltr">On Sat, Dec 12, 2015 at 6:20 PM Matthew Johnson via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
> I mean, I don't know about you, but I get called in to look at projects regularly that have a MainViewController.swift that weighs 10KLOC. I didn't write it. I didn't make the mess. I just want tools to help me clean it up. 'private' is useless in that context, and it's a (sadly) typical context in iOS.<br>
<br>
+1. Messes like this are all too common in the real world.<br>
<br>
Even worse, they often involve poorly thought out uses of uses of inheritance. We need tools to help clean them up and also a language designed to make it more difficult to unintentionally create them in the first place. This is a very non-trivial part of the argument for making final the default IMO.<br>
<br>
Matthew<br>
<br>
_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org" target="_blank">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>
</blockquote></div>