<div dir="ltr">@Aron, I did take a look at that document while developing the proposal. As you stated, it's a little old, however the principles of access control and their purpose remain pretty much the same. <div><br></div><div>".keep private details of a class hidden from the rest of the app</div><div> .keep interna details of a framework hidden from the client app"</div><div><br></div><div>Both these rules still get respected with the introduction of a new level of access control. <b>typeprivate </b>would not allow for member access within any other then the <b>type</b> itself.</div><div><br></div><div>@Jay, while I do appreciate your idea, I'm afraid this proposal aims at something a lot less complex. One may argue the changes in Swift's design to accommodate it may facilitate and open door to more complex changes like the one you suggest, still I believe those changes are most welcome in the name creating a safer and easier to handle access control policy. This proposal aims only at opening access to private members to any extension over that type.</div></div><div class="gmail_extra"><br><div class="gmail_quote">2016-12-01 17:47 GMT+00:00 Martin Waitz via swift-evolution <span dir="ltr"><<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<span class=""><br>
Am 2016-12-01 11:08, schrieb Álvaro Monteiro via swift-evolution:<br>
> - Typeprivate would allow to abandon the odd fileprivate. Access level<br>
> would be constrained to swift constructs (structs, classes and<br>
> extensions) and not to a compiler artifact (file).<br>
<br>
</span>Files are not compiler artifacts but design artifacts.<br>
They group related stuff which was designed together and which should be reviewed together.<br>
<br>
I really like `fileprivate` and how Swift currently handles access control.<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Martin<br>
</font></span><div class="HOEnZb"><div class="h5">______________________________<wbr>_________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/<wbr>mailman/listinfo/swift-<wbr>evolution</a><br>
</div></div></blockquote></div><br></div>