<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><br class=""><blockquote type="cite" class=""><div class=""><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">Also, while some have mentioned that this adds complexity to the access control system because types are now a factor, to that I say: this is purely a theoretical issue. In practice, developers don't<span class="Apple-converted-space"> </span><i class="">care</i><span class="Apple-converted-space"> </span>that this is case, and just care that the access control logic makes sense when using it. As someone who's had to explain why fileprivate is necessary many times to new Swift developers when using extensions, I can assure you that using this proposed private definition makes more<span class="Apple-converted-space"> </span><i class="">intuitive</i><span class="Apple-converted-space"> </span>sense to them.</div></div></blockquote></div>Well, I guess than it would be the best to ignore private completely and only teach the model of Swift 2:<div class="">Without private, access control is completely separated from from extensions (mixing concerns rarely makes things easier), and you save yourself from the questions why extension A can't see a property declared five lines above, wheres extension B at the bottom of the same file has no such problem.</div><div class="">No one really knows what's better for the "average Swift programmer", and no matter how many newcomers you have met, I doubt it is a significant share of all Swift users out there.</div><div class=""><br class=""></div><div class="">Sticking to facts, we have a steady increase of access control complexity, and this is pepped by adding special rules to work around perceived or real inconveniences.</div><div class="">SE-0169 aims to be a small change with minimal impact, but those pile up easily...</div></body></html>