<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="">On Oct 2, 2017, at 5:33 PM, Jordan Rose <<a href="mailto:jordan_rose@apple.com" class="">jordan_rose@apple.com</a>> wrote:<br class=""><div><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><blockquote type="cite" class=""><div class=""><div class=""><br class="">Don't you think this is not normal situation and actually there IMO can't be any reason to keep this bug-producing inconsistency in Swift? (especially given Swift 5 seems like is a last moment to fix this)</div></div></blockquote><br class=""></div><div class="">I hate to say it but I'm inclined to agree with Vladimir on this. "private extension" has a useful meaning now distinct from "fileprivate extension", and it was an oversight that <a href="https://github.com/apple/swift-evolution/blob/master/proposals/0169-improve-interaction-between-private-declarations-and-extensions.md" class="">SE-0169</a> didn't include a fix here. On this <i class="">very narrow, very specific </i>access control issue I think it would still be worth discussing; like Xiaodi said it's not related to James' original thread-starter.</div></div></div></blockquote><br class=""></div><div>Ok, I admit I just didn’t want to think about access control anymore after laster year’s excitement :-)</div><div><br class=""></div><div>That said, it seems that there is broad support for considering a refinement here, and I’m happy to get out of the way and let you guys make Swift better. :-) Thanks!</div><div><br class=""></div><div>-Chris</div><div><br class=""></div><br class=""></body></html>