<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><b class="">What is your evaluation of the proposal?<br class=""></b></div><div class=""><b class=""><br class=""></b></div><div class="">-1. I disagree with the starting motivation points, so it's hard to really see the value in the rest of the arguments.</div><div class=""><b class=""><br class=""></b></div><div class=""><b class="">Is the problem being addressed significant enough to warrant a change to Swift?<br class=""></b></div><div class=""><br class=""></div><div class="">No.</div><div class=""><b class=""><br class=""></b></div><div class=""><b class="">Does this proposal fit well with the feel and direction of Swift?<br class=""></b></div><div class=""><b class=""><br class=""></b></div><div class="">No. Swift's access modifier control is about code unit access levels. This proposal breaks this conceptual model. Now instead of thinking of publicly exposed APIs, APIs using only within the context of the module, and APIs local to the file, I now need to parse semantic scopes to understand where a piece of code can be used.</div><div class=""><br class=""></div><div class="">Basically Swift's model is:</div><div class=""> - public exports</div><div class=""> - internal exports</div><div class=""> - no exports</div><div class=""><br class=""></div><div class="">This proposal doesn't fit anywhere in that model.</div><div class=""><b class=""><br class=""></b></div><div class=""><b class="">If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?<br class=""></b></div><div class=""><br class=""></div><div class="">Yes, this basically what private is other languages. However, traditionally "private scope" implementations have severe weaknesses in the ability to expose the implementation details only to helper code within the same file. Creating local re-invents part of that. </div><div class=""><br class=""></div><div class=""><b class="">How much effort did you put into your review? A glance, a quick reading, or an in-depth study?</b></div><div class=""><b class=""><br class=""></b></div><div class="">I've read the review and followed much of the conversation, including participating in the previous thread on this topic.</div></body></html>