[swift-evolution] [Accepted] SE-0169: Improve Interaction Between `private` Declarations and Extensions
jordan_rose at apple.com
Thu Apr 20 13:33:12 CDT 2017
> On Apr 18, 2017, at 20:40, Douglas Gregor via swift-evolution <swift-evolution at swift.org> wrote:
> This makes the private/fileprivate distinction meaningful for extensions. I think also bans the use of "private" at global scope for non-nominal types or extensions thereof. A clarifying update to the proposal is in order, so developers can better understand the semantics.
Wait, hang on, then people have to write 'fileprivate' instead of 'private' for top-level typealiases (and functions?). Apart from whether or not that's desirable, it's not backwards-compatible.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-evolution