<div dir="ltr">I have to agree with you. Still "module" needs to be somewhere in the new access level for internal, and if possible, "file" in private.</div><div class="gmail_extra"><br><div class="gmail_quote">2016-03-15 16:07 GMT+03:00 Ilya Belenkiy <span dir="ltr"><<a href="mailto:ilya.belenkiy@gmail.com" target="_blank">ilya.belenkiy@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">These names are very uniform, and the context is immediately clear, but they are very long. The 2 most commonly used (and spelled out) would be access(global) and access(scope), public and private are much shorter and are well established terms of art.<br><div class="gmail_quote"><div><div class="h5"><div dir="ltr">On Tue, Mar 15, 2016 at 8:54 AM Антон Жилин <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:<br></div></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr"><div>My take at it:</div><div><br></div><div>access(global)</div><div>access(module) // default</div><div>access(file)</div><div>access(scope)</div><div><br></div><div>Very uniform. Argument to `access` is visibility scope.</div></div></div></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>
</blockquote></div><br></div>