<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><br class=""></div><div class=""><b class="">• What is your evaluation of the proposal?</b></div><div class="">+1</div><div class=""><br class=""></div><div class=""><b class="">• Is the problem being addressed significant enough to warrant a change to Swift?</b></div><div class=""><br class=""></div><div class="">Yes. For some strange reason, i can’t bring myself to write `fileprivate` instead of `private` by default - if i don’t specifically think of it, i end up with privates everywhere, and then have to go back and change to `fileprivate`. At times, it seems a bit annoying.</div><div class=""><br class=""><b class="">• Does this proposal fit well with the feel and direction of Swift?</b></div><div class=""><b class=""><br class=""></b></div><div class="">Oh yes. <span style="color: rgb(186, 45, 162); font-family: Menlo; font-size: 11px;" class="">fileprivate</span> is too long a word for access level that i pretty much use as a default; and definitely not intuitive.</div><div class=""><br class=""></div><div class="">I write as much framework code, as application logic. Since Swift 3 i don’t remember many cases where i <i class="">had to</i> use `private`. I do, however, have many `private` members in my code - solely because `private` is way more <i class="">intuitive</i> to write.</div><div class=""><br class=""></div><div class="">~99% of privates in my code are there by mistake - but thats what i end up with. That means, there is no need for a mixed code like that 99% of the time:</div><div class=""><br class=""></div><div class=""><div style="margin: 0px; font-size: 11px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class=""> </span><span style="font-variant-ligatures: no-common-ligatures; color: #ba2da2" class="">private(set)</span><span style="font-variant-ligatures: no-common-ligatures" class=""> </span><span style="font-variant-ligatures: no-common-ligatures; color: #ba2da2" class="">var</span><span style="font-variant-ligatures: no-common-ligatures" class=""> iosAudio: </span><span style="font-variant-ligatures: no-common-ligatures; color: #703daa" class="">CMSampleBuffer</span><span style="font-variant-ligatures: no-common-ligatures" class="">?</span></div><div style="margin: 0px; font-size: 11px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class=""> </span><span style="font-variant-ligatures: no-common-ligatures; color: #ba2da2" class="">private(set)</span><span style="font-variant-ligatures: no-common-ligatures" class=""> </span><span style="font-variant-ligatures: no-common-ligatures; color: #ba2da2" class="">var</span><span style="font-variant-ligatures: no-common-ligatures" class=""> iosVideo: </span><span style="font-variant-ligatures: no-common-ligatures; color: #703daa" class="">CMSampleBuffer</span><span style="font-variant-ligatures: no-common-ligatures" class="">?</span></div><div style="margin: 0px; font-size: 11px; line-height: normal; font-family: Menlo; color: rgb(186, 45, 162);" class=""><span style="font-variant-ligatures: no-common-ligatures; color: #000000" class=""> </span><span style="font-variant-ligatures: no-common-ligatures" class="">fileprivate(set)</span><span style="font-variant-ligatures: no-common-ligatures; color: #000000" class=""> </span><span style="font-variant-ligatures: no-common-ligatures" class="">var</span><span style="font-variant-ligatures: no-common-ligatures; color: #000000" class=""> mic: </span><span style="font-variant-ligatures: no-common-ligatures; color: #703daa" class="">CMSampleBuffer</span><span style="font-variant-ligatures: no-common-ligatures; color: #000000" class="">?</span></div><div style="margin: 0px; font-size: 11px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class=""> </span><span style="font-variant-ligatures: no-common-ligatures; color: #ba2da2" class="">fileprivate(set)</span><span style="font-variant-ligatures: no-common-ligatures" class=""> </span><span style="font-variant-ligatures: no-common-ligatures; color: #ba2da2" class="">var</span><span style="font-variant-ligatures: no-common-ligatures" class=""> serialNumber: </span><span style="font-variant-ligatures: no-common-ligatures; color: #703daa" class="">String</span></div><div style="margin: 0px; font-size: 11px; line-height: normal; font-family: Menlo; color: rgb(186, 45, 162);" class=""><span style="font-variant-ligatures: no-common-ligatures; color: #000000" class=""> </span><span style="font-variant-ligatures: no-common-ligatures" class="">fileprivate(set)</span><span style="font-variant-ligatures: no-common-ligatures; color: #000000" class=""> </span><span style="font-variant-ligatures: no-common-ligatures" class="">var</span><span style="font-variant-ligatures: no-common-ligatures; color: #000000" class=""> name: </span><span style="font-variant-ligatures: no-common-ligatures; color: #703daa" class="">String</span></div></div><div class=""><br class=""></div><div class="">It also means, the 1% where i <i class="">want</i> to use `private`, the readers/users of my code may think it's a mistake too.</div><div class=""><br class=""></div><div class="">My point of view, the number of times i mean "this variable or function can only be accessed from within tis file" dwarfs the number when i mean "it can only be accessed by subclasses". They don't even compare.</div><div class=""><br class=""></div><div class="">If enough people need access based on class hierarchy, we should pick a keyword specifically for that - like "classprivate" if you will. But private within the file simply makes more sense.</div><div class=""><br class=""><b class="">• If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to<br class="">those?</b></div><div class="">N/A</div><div class=""><br 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 have strong opinion based on how i use Swift, which i love deep from the heart. </div><div class=""><br class=""></div><div class="">Thanks David & Doug for giving hope this may actually be reverted.</div><br class=""></body></html>