[swift-evolution] SE-0025: Scoped Access Level, next steps
jordan_rose at apple.com
Fri Mar 25 11:51:52 CDT 2016
> On Mar 25, 2016, at 9:46, Ross O'Brien <narrativium+swift at gmail.com> wrote:
> Well, several prominent voices seem to think that 'private' is "intuitively obvious" when it refers to declaration-level scope, so I didn't argue that point. I still happen to disagree; I would add 'privatetodeclaration' to 'privatetomodule' and 'privatetofile', which would solve that conversational point: "These properties are private to the declaration".
> Alternatively: 'fileaccessible', 'moduleaccessible', 'declarationaccessible'? (Does that confuse code accessibility with such things as UIAccessibility?)
Just on this point, yes, we've been advised to avoid the word "accessibility" in the past. We're deliberately using "access control" and "access"; "accessible" is kind of on the line.
(We're not using "visible" because whether something is "visible" depends on the use site, whereas access level is a characteristic of the declaration only.)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-evolution