On Oct 2, 2017, at 5:33 PM, Jordan Rose <[email protected]> wrote: >> >> 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) > > 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 SE-0169 > <https://github.com/apple/swift-evolution/blob/master/proposals/0169-improve-interaction-between-private-declarations-and-extensions.md> > didn't include a fix here. On this very narrow, very specific access control > issue I think it would still be worth discussing; like Xiaodi said it's not > related to James' original thread-starter.
Ok, I admit I just didn’t want to think about access control anymore after laster year’s excitement :-) 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! -Chris
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
