<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=""><br class=""><div><blockquote type="cite" class=""><div class=""> That’s why open is a success IMHO</div></blockquote>I always appreciate when personal opinion is marked — I just want to point out this could apply to two aspects here ("that's why" and "open is a success" ;-)<br class=""><div><br class=""></div><blockquote type="cite" class=""><div class=""><span 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; float: none; display: inline !important;" class="">I don’t think its worth arguing about renaming again. Yes, its technically a better option, </span></div></blockquote><div>There's rarely complete agreement about anything, but exceptions aside: Is there consensus about this?</div><div>If that's actually the case, I think we really should take a step back and question ourselves:</div><div>This would mean Swift discards a compromise which was afaics widely accepted in favour of something worse because… it is to much work and the "other languages" would laugh about our fickleness?</div><div>And would keeping status quo be so much worse than status quo with new names?</div><div>I'm not sure about the longevity of the Swift 4 model of access control (however it may look like), but afaik, we might have to live with it for a long time — and many future users of Swift (without any legacy-knowledge) as well. </div><div><br class=""></div><blockquote type="cite" class=""><div class=""><span 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; float: none; display: inline !important;" class="">but the Core Team will not consider it for the same reasons they rejected SE-0159. I’m under the impression that SE-0169 is the only solution we have.</span></div></blockquote></div><br class=""><div class=""><br class=""></div></body></html>