On Mar 24, 2016, at 6:10 PM, Brent Royal-Gordon via swift-evolution <swift-evolution@swift.org> wrote:
> Honestly, though, I'm not sure why people are working so hard to cram > `private` in there. Does `moduleprivate` or `private(module)` really convey > more information than `module`? Particularly once you've looked it up and > know that it's an access modifier? > > -- > Brent Royal-Gordon > Architechies > > _______________________________________________ > swift-evolution mailing list > swift-evolution@swift.org > https://lists.swift.org/mailman/listinfo/swift-evolution I'm with you here too. I'm not opposed to it but it strikes me as being hypertechnical and unnecessarily verbose. It's also not symmetrical: where is modulepublic and filepublic? Those don't make sense? Then module and file stand on their own if private is implied (you know people will wonder when they see moduleprivate if a public one exists) Brandon _______________________________________________ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution
