> On Mar 23, 2016, at 11:13 PM, Chris Lattner via swift-evolution
> <swift-evolution@swift.org> wrote:
> How about we continue this trend, and follow other existing Swift keywords
> that merge two lowercase words (associatedtype, typealias, etc), and use:
>
> public
> moduleprivate
> fileprivate
> private
>
> The advantages, as I see them are:
> 1) We keep public and private meaning the “right” and “obvious” things.
> 2) The declmodifiers “read” correctly.
> 3) The unusual ones (moduleprivate and fileprivate) don’t use the awkward
> parenthesized keyword approach.
> 4) The unusual ones would be “googable”.
> 5) Support for named submodules could be “dropped in” by putting the
> submodule name/path in parens: private(foo.bar.baz) or
> moduleprivate(foo.bar). Putting an identifier in the parens is much more
> natural than putting keywords in parens.
I support this for all the enumerated reasons. This is clean, simple, and
obvious.
It retains the benefits and avoids the negatives of the parenthesized versions.
One correction: "googlable" not "googable", because that's how pedants roll.
(cite: https://en.wikipedia.org/wiki/Muphry%27s_law
<https://en.wikipedia.org/wiki/Muphry's_law>)
-- E
_______________________________________________
swift-evolution mailing list
swift-evolution@swift.org
https://lists.swift.org/mailman/listinfo/swift-evolution
