[swift-evolution] SE-0025: Scoped Access Level, next steps
erica at ericasadun.com
Tue Mar 15 15:33:44 CDT 2016
Global visibility, private settable public private(set) var foo: String
Global visibility, module settable public private(module set) var foo: String
Module visibility, file settable private(module, file set) var foo: String
of course if module visibility is the default, that might be instead:
Module visibility, file settable private(file set) var foo: String
> On Mar 15, 2016, at 2:14 PM, David Waite via swift-evolution <swift-evolution at swift.org> wrote:
> I like the idea of public and then varying degrees of private (with the default being the most private). Public values are published outside of the build target.
> However, I have a question how we would express the concept of mixed property access levels, for instance with a private (to the scope) setter and private (to the module) getter.
>> On Mar 14, 2016, at 6:49 PM, James Berry via swift-evolution <swift-evolution at swift.org <mailto:swift-evolution at swift.org>> wrote:
>> private symbol visible within the current declaration (class, extension, etc).
>> private(module) symbol visible within the current module.
>> private(file) symbol visible within the current file.
>> swift-evolution mailing list
>> swift-evolution at swift.org <mailto:swift-evolution at swift.org>
>> https://lists.swift.org/mailman/listinfo/swift-evolution <https://lists.swift.org/mailman/listinfo/swift-evolution>
> swift-evolution mailing list
> swift-evolution at swift.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-evolution