[swift-evolution] SE-0025: Scoped Access Level, next steps
Erica Sadun
erica at ericasadun.com
Tue Mar 15 16:05:34 CDT 2016
I see two results on the gmane search and neither one seems to match what you're talking about:
http://search.gmane.org/?query=Scoped&author=Shawn&group=gmane.comp.lang.swift.evolution&sort=relevance <http://search.gmane.org/?query=Scoped&author=Shawn&group=gmane.comp.lang.swift.evolution&sort=relevance>
Do you have a direct link to the message I should be reading?
Thanks!
-- Erica
> On Mar 15, 2016, at 2:42 PM, Shawn Erickson <shawnce at gmail.com> wrote:
>
> See my email earlier in this thread about how to potentially deal with this leveraging fairly normal syntax we already have to support in swift.
>
> On Tue, Mar 15, 2016 at 1:34 PM Erica Sadun via swift-evolution <swift-evolution at swift.org <mailto:swift-evolution at swift.org>> wrote:
> Oddball cases:
>
> 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
>
> -- E
>
>> On Mar 15, 2016, at 2:14 PM, David Waite via swift-evolution <swift-evolution at swift.org <mailto: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.
>>
>> -DW
>>
>>> 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.
>>>
>>> James
>>> _______________________________________________
>>> 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 <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 <mailto:swift-evolution at swift.org>
> https://lists.swift.org/mailman/listinfo/swift-evolution <https://lists.swift.org/mailman/listinfo/swift-evolution>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160315/2efd6065/attachment.html>
More information about the swift-evolution
mailing list