[swift-evolution] SE-0025: Scoped Access Level, next steps

[Michael Wells]

I know that it’s been suggested a while back, but what is/was the reasoning for rejecting:

public
module (same as internal in Swift 2.2)
file (same as private in Swift 2.2)
private

It seems pretty simple, clear, and understandable. It doesn’t make itself very useful as search terms (module or file are pretty generic), but I would assume that would be a learn-once-and-your-done thing.
—
Michael Wells


> On Mar 30, 2016, at 5:24 PM, Brent Royal-Gordon via swift-evolution <swift-evolution at swift.org> wrote:
> 
>> I maintain that anyone with a coding convention of "always write an access modifier" will be very upset with this.
> 
> I doubt they'll be too pleased with `moduleprivate`, either.
> 
> -- 
> Brent Royal-Gordon
> Architechies
> 
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160330/9dc021a3/attachment.html>