[swift-evolution] [Review] SE-0025 Scoped Access Level

Rob Mayoff mayoff at dqd.com
Sun Feb 28 23:37:58 CST 2016


>
> Proposal link:
>
>
> https://github.com/apple/swift-evolution/blob/master/proposals/0025-scoped-access-level.md
>
>
>    - What is your evaluation of the proposal?
>
> I am very in favor of an access control modifier with the effect described
in the proposal. The proposal addresses a shortcoming of the Swift language
which I have felt acutely many times. I am not particularly attached to the
specific word “local” as the modifier.


>
>    - Is the problem being addressed significant enough to warrant a
>    change to Swift?
>
> Yes.


>
>    - Does this proposal fit well with the feel and direction of Swift?
>
> Yes. It conveys an important intent to the compiler for enforcement with
minimal impact to the style and structure of the language.

There are other features that I hope to someday see in Swift that would
sometimes replace the need for this (e.g. nested modules). Even so, I think
there will always be cases where this level of access control conveys
useful information.


>
>    - If you have used other languages or libraries with a similar
>    feature, how do you feel that this proposal compares to those?
>
> Of the languages I've used heavily, C++, Java, and Scala have a similar
level of access control. Scala has the finest granularity of access control
amongst the languages I've used. Scala has more access control granularity
than I've ever needed, but Swift has less than I've wanted. This proposal
improves Swift without going overboard.


>
>    - How much effort did you put into your review? A glance, a quick
>    reading, or an in-depth study?
>
> I read the proposal carefully. I also followed the original discussion
closely and participated in it.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160228/f2b55036/attachment.html>


More information about the swift-evolution mailing list