<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><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="">I agree, but after having originally raised the issue, members of the core team clearly disagreed. Therefore, it's clear that this is going to have to go through Swift Evolution or not be changed at all. And I also agree with the notion that further discussions of access modifiers, which will most certainly lead to a rehash of the whole sordid past, is unhealthy.</div></div></blockquote></div>I guess that is the price to pay for stability… I personally am quite sad that Swift reached that phase already.<div class="">But who knows — maybe after some years of collecting legacy, this might be discussed again in a cleanup release of Swift.</div><div class=""><br class=""></div><div class="">Still, I think the current situation is a pity, as everyone seems to agree that we ended up with a flawed solution for access control :-(</div></body></html>