> On Mar 24, 2016, at 1:13 AM, Chris Lattner via swift-evolution
> <[email protected]> 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.
+1. It also has the advantage of getting rid of the confusing distinction
between “private” and “internal”—which is backwards from the usual
“API/SPI/IPI” terminology.
-Colin
_______________________________________________
swift-evolution mailing list
[email protected]
https://lists.swift.org/mailman/listinfo/swift-evolution
