>> On Mon, Mar 14, 2016 at 8:18 PM Chris Lattner via swift-evolution
>> <[email protected]> wrote:
>>> Per Doug’s email, the core team agrees we should make a change here, but
>>> would like some bikeshedding to happen on the replacement name for private.
>>>
>>> To summarize the place we’d like to end up:
>>>
>>> - “public” -> symbol visible outside the current module.
>>> - “internal” -> symbol visible within the current module.
>>> - unknown -> symbol visible within the current file.
>>> - “private” -> symbol visible within the current declaration (class,
>>> extension, etc).
I'm tempted to wade in on the KISS principle with :
public
internal
file
private
"It does what it says on the tin" :-)
Joanna
Carter Consulting
Envoyé de mon iPad
_______________________________________________
swift-evolution mailing list
[email protected]
https://lists.swift.org/mailman/listinfo/swift-evolution
