Agreed, seems like a good way to go. [[iOS messageWithContent:webContent] broadcast]
> On 24 Mar 2016, at 07:04, David Hart via swift-evolution > <[email protected]> wrote: > > I like it very much. > >> On 24 Mar 2016, at 06:13, 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. >> >> What do you all think? > > _______________________________________________ > swift-evolution mailing list > [email protected] > https://lists.swift.org/mailman/listinfo/swift-evolution
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
