[swift-evolution] [swift-evolution-announce] [Review] SE-0159: Fix Private Access Levels

[Vanderlei Martinelli]

   - What is your evaluation of the proposal?

Huge +1.

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

Yes. I would like to see the `private` as it was before (and introduce a
new `local` keyword for scoped access, but that is another history).

   - Does this proposal fit well with the feel and direction of Swift?

For sure.

   - If you have used other languages or libraries with a similar feature,
   how do you feel that this proposal compares to those?

Swift 1.x and Swift 2.x. It is different from other programming languages,
but it is already incorporated by the Swift developers.

   - How much effort did you put into your review? A glance, a quick
   reading, or an in-depth study?

I read the proposal when it was first presented and have followed many,
many threads about both the proposal and about 'private' and 'fileprivate'
on the lists.


On Mon, Mar 20, 2017 at 8:54 PM, Douglas Gregor <dgregor at apple.com> wrote:

> Hello Swift community,
>
> The review of SE-0159 "Fix Private Access Levels" begins now and runs
> through March 27, 2017. The proposal is available here:
>
> https://github.com/apple/swift-evolution/blob/master/
> proposals/0159-fix-private-access-levels.md
>
> Reviews are an important part of the Swift evolution process. All reviews
> should be sent to the swift-evolution mailing list at
>
> https://lists.swift.org/mailman/listinfo/swift-evolution
>
> or, if you would like to keep your feedback private, directly to the
> review manager. When replying, please try to keep the proposal link at the
> top of the message:
>
> Proposal link:
>
> https://github.com/apple/swift-evolution/blob/master/
> proposals/0159-fix-private-access-levels.md
>
> Reply text
>
> Other replies
>
>
> <https://github.com/apple/swift-evolution/blob/master/process.md#what-goes-into-a-review-1>What
> goes into a review?
>
> The goal of the review process is to improve the proposal under review
> through constructive criticism and, eventually, determine the direction of
> Swift. When writing your review, here are some questions you might want to
> answer in your review:
>
>    - What is your evaluation of the proposal?
>    - Is the problem being addressed significant enough to warrant a
>    change to Swift?
>    - Does this proposal fit well with the feel and direction of Swift?
>    - If you have used other languages or libraries with a similar
>    feature, how do you feel that this proposal compares to those?
>    - How much effort did you put into your review? A glance, a quick
>    reading, or an in-depth study?
>
> More information about the Swift evolution process is available at
>
> https://github.com/apple/swift-evolution/blob/master/process.md
>
> Thank you,
>
> -Doug
>
> Review Manager
>
> _______________________________________________
> swift-evolution-announce mailing list
> swift-evolution-announce at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution-announce
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20170320/7e451d9a/attachment.html>