This idea has been discussed before and deemed inconsistent with Swift's design for access levels. Any further access levels are pretty clearly out of scope for Swift 5. I'll refer you to the list of focus areas here:<br><br><a href="https://github.com/apple/swift-evolution">https://github.com/apple/swift-evolution</a><br><br><br><div class="gmail_quote"><div dir="ltr">On Mon, Oct 30, 2017 at 20:30 Mike Kluev 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 dir="ltr">On 31 October 2017 at 00:36, Noah Desch <span dir="ltr"><<a href="mailto:deschnl@icloud.com" target="_blank">deschnl@icloud.com</a>></span> wrote:<br></div><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><span class="m_-4080387625893841521gmail-"><br>
<br>
> On Oct 30, 2017, at 6:38 PM, Adam Kemp via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:<br>
><br>
><br>
><br>
>> On Oct 30, 2017, at 2:23 PM, Mike Kluev <<a href="mailto:mike.kluev@gmail.com" target="_blank">mike.kluev@gmail.com</a>> wrote:<br>
>><br>
>> On 30 October 2017 at 19:49, Adam Kemp <<a href="mailto:adam_kemp@apple.com" target="_blank">adam_kemp@apple.com</a>> wrote:<br>
>><br>
>> How do you know there’s not an extension in this file without looking? If you don’t know then you have to check. That puts it in the same bucket as internal or public. The set of files you have to search through for usages is the same.<br>
>><br>
>><br>
>> I'd just search for "extension SomeClass", Xcode search result window will list all files that have it.<br>
>> or I will list all the users of "foo" if that's the one I am changing.<br>
><br>
> When you do that search, which files do you include in the search? That’s the key.<br>
<br>
<br>
</span>If I’m concerned with how much work I’ll have to do, no that’s not the key. The key is how many files do I have to read myself (only those containing a subclass or extension of my base class). You seem to be conflating a near instantaneous search in an IDE with manually evaluating a change’s impact to other source files in the module. “Classprivate" makes significantly fewer files that I have to manually review compared to “internal”.</blockquote><div><br></div></div></div></div><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>exactly. significantly fewer files or fragments of files - significantly fewer entries in the search results in other words.</div><div><br></div><div>when in a pub:</div><div><br></div><div>public / internal:</div><div> - may i have a pint of lager please? - sure, here you are</div><div><br></div><div>classprivate / protected:</div><div> - may i have a pint of ale please?</div><div> - sure. are you a member of our club? we serve ale to members only</div><div> - errr. no. can i become a member?</div><div> - yes, it is free. just take a seat over there and fill this form first, once done i will bring you your ale.</div><div> - errr, thanks. may i have lager instead please?</div><div><br></div><div>private:</div><div><div> - may i have a pint of potter please?</div></div><div> - sure. are you a member of our club?</div><div> - yes, i just filed the form, here it is.</div><div> - are you aware that we serve potter only in that "core members only" private room?</div><div> - errr, no, how do i get there?</div><div> - ah, no sir, it is impossible. you would know if you can go there. it is by invitation only system.</div><div> - damn!! lager!</div><div><br></div><div>i am dead sure they will serve much less ale than lager, don't you.</div></div></div></div><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><br></div><div>Mike</div><div><br></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>