[swift-evolution] [swift-evolution-announce] [Review] SE-0159: Fix Private Access Levels

Matthew Johnson matthew at anandabits.com
Thu Mar 23 10:54:53 CDT 2017

> On Mar 23, 2017, at 10:51 AM, Andrey Fidrya via swift-evolution <swift-evolution at swift.org> wrote:
>> On 23 Mar 2017, at 05:18, Nevin Brackett-Rozinsky via swift-evolution <swift-evolution at swift.org> wrote:
>> I strongly prefer that “private” should mean “visible in the current file”.
>> I am ambivalent between eliminating the scoped access level or renaming it “scoped”, as long as “private” once more denotes file-level visibility.
> Imo opinions are split 50/50 on whether access levels should be file based or type based, it's endless debate.
> What are the downsides of covering both cases? I.e. making private "visible in the current file and type extensions".
> This concept is not that hard to teach and doesn't require complex and syntactically verbose access level systems.

I can’t speak for others, but I want scoped access not type-based access.  Type-based access control solves different problems than scoped access control and isn’t under discussion in this review.

> Andrey
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution

More information about the swift-evolution mailing list