<div style="white-space:pre-wrap">Please take a look at the other posts today. I addressed this concern earlier. In one sentence, just like you wouldn't want to put every paragraph of a book or every section of an article in an encyclopedia in a separate file, you wouldn't want to end up with a gazillion files just to ensure that implementation details of an API stay hidden in a way that is enforced by the compiler.<br><br>--<br>Ilya Belenkiy</div><br><div class="gmail_quote"><div dir="ltr">On Mon, Dec 14, 2015 at 2:19 PM Colin Cornaby 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"><div><div>(I'm reading the upstream discussion but I'll reply here.)</div><div><br></div><div>I don't know if I really like the pattern this is trying to support. I like that Swift makes it cleaner to include multiple types in a single Swift file. But I feel like this proposal is trying to take things too far the other way. Types that should should only see each other from a non "friends" role should be in separate files.</div><div><br></div><div>What's proposed doesn't really harm someone who likes the "multiple file" style directly, but I don't want to see projects where everything gets jammed into one file. I think keeping the scope of private (with no new keywords) to the same file encourages good coding practices.</div><div><br></div><div>I've really liked the balance Swift strikes in this case. I feel like this discussion is going to come down to opinion, but projects that I've worked in that have tried to over compact have always run into issues. I don't know if it's the role of the language to push an ideology either way, but personally I like the direction Swift is pushing. Files make for good scope boundaries.</div><div><br>On Dec 05, 2015, at 08:40 PM, Ilya via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:<br><br></div><div><blockquote type="cite"><div><div dir="ltr">I think the it would help a great deal to have an access level modifier that is really private and visible only inside the class itself. Right now, the only way to hide implementation details for a class is to hide the class code in a separate file, which is very inconvenient for several reasons:<div><br></div><div>1) the meaning of the code changes depending on which file the class is in. It's very easy to accidentally expose class internal details and then call class elements that are meant to be used only inside the class. Having a keyword for class internals will allow the compiler to ensure that only the public API for the class is used from the outside world. The user can check types on his own, but it's better that the compiler does it automatically. Similarly, the user can check that only the proper APIs are called, but it's better that the compiler does it automatically.</div><div><br></div><div>2) accessibility by file structure may cause some really short files. </div><div><br></div><div>3) It's impossible to group related classes in one file but still hide implementation details inside each class</div><div><br></div><div>I think that it the best solution is to make private keyword do what it states -- keep the class element private to the class. But if it's really important to have a separate keyword for backward compatibility, it would be the next best thing.</div><div><br></div><div>--</div><div>Ilya Belenkiy</div></div></div></blockquote></div></div><div><div><blockquote type="cite"><div><img src="https://u2002410.ct.sendgrid.net/wf/open?upn=OFgvmg1J6naJevMotmPmRgzA4p1gcL5s2O89Xj3c0DTNHsqJk65QFT5HLCVezTEprPcloGEz-2Br9eX025xVr0O5djiNmvDtObklmVeX-2B1GNTS-2Fnw4G-2Firawot5vOYNnJx8VglVzjCO6FF-2FWlpJIhHkHCuoca6ZlHSegHCts96VVjE5sXIc07iEl3EfeNiUlweed2WOO2xFh-2BwEhkqg0XL3CwYKxPpCifcnwHp4APtgA0-3D" alt="" width="1" height="1" border="0" style="min-height:1px;width:1px;border-width:0;padding:0;margin:0"><div><span>_______________________________________________<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" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br></span></div></div></blockquote></div></div><div><div><blockquote type="cite"><div></div></blockquote></div>
<img src="https://u2002410.ct.sendgrid.net/wf/open?upn=JoVvr1nwtkf-2FcycRIsh0Ekp6hrdbCH7iUjVG-2FENQSue2nvVSO-2F4L-2BUCQGbPHKghVUHW0pZgfgNYXmZTSz-2BC2vyXP6nhyBw7usZnDdbIvoPVlyVwjyfcAbDDklTZofD5QfRFvZxaKbKvzHw4c50WGtaag0-2F8oF0qikJFMmdTF8-2FDORfoqqkWlntN3UMyY5xS8fWk4tgeEy4pJwmyoZC1GfW7BlpnhXwJNYTexCegg1Xs-3D" alt="" width="1" height="1" border="0" style="min-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>
_______________________________________________<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>