<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Mar 23, 2016, at 11:13 PM, Chris Lattner via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><div class=""><div class="">How about we continue this trend, and follow other existing Swift keywords that merge two lowercase words (associatedtype, typealias, etc), and use:<br class=""><br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>public<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>moduleprivate<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>fileprivate<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>private<br class=""><br class="">The advantages, as I see them are:<br class="">1) We keep public and private meaning the “right” and “obvious” things.<br class="">2) The declmodifiers “read” correctly.<br class="">3) The unusual ones (moduleprivate and fileprivate) don’t use the awkward parenthesized keyword approach.<br class="">4) The unusual ones would be “googable”.<br class="">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.<br class=""></div></div></blockquote></div><br class=""><div class="">I support this for all the enumerated reasons. This is clean, simple, and obvious. </div><div class="">It retains the benefits and avoids the negatives of the parenthesized versions.</div><div class=""><br class=""></div><div class="">One correction: "googlable" not "googable", because that's how pedants roll. </div><div class="">(cite: <a href="https://en.wikipedia.org/wiki/Muphry's_law" class="">https://en.wikipedia.org/wiki/Muphry%27s_law</a>)</div><div class=""><br class=""></div><div class="">-- E</div></body></html>