[swift-evolution] [Review] SE-0169: Improve Interaction Between private Declarations and Extensions

[Goffredo Marocchi]

+1 this is perhaps the best compromise between the two views on access control I have seen in a while and the change is actually very tiny yet meaningful. Thanks David and Chris!

Sent from my iPhone

> On 7 Apr 2017, at 00:10, Douglas Gregor via swift-evolution <swift-evolution at swift.org> wrote:
> 
> Hello Swift community,
> 
> The review of SE-0169 "Improve Interaction Between private Declarations and Extensions" begins now and runs through April 11, 2017. The proposal is available here:
> 
> https://github.com/apple/swift-evolution/blob/master/proposals/0169-improve-interaction-between-private-declarations-and-extensions.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/0169-improve-interaction-between-private-declarations-and-extensions.md
> Reply text
> Other replies
> 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?
+1 this is something that would make the language more pleasing to use and easier to learn and code well in.

> Is the problem being addressed significant enough to warrant a change to Swift?
Yes, we have a rare chance to adjust something that represented a pain point and brought lots of arguing back and forth in the community. It is time to move past it and give it the help it needs.

> Does this proposal fit well with the feel and direction of Swift?
I think it does yes.

> If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?
It makes private and fileprivate belong in the language and help it stay true to its progressive disclosure and architecture goals while being more inviting to users coming from other super mainstream programming languages which facilitate the cross pollination of ideas and talent.

> How much effort did you put into your review? A glance, a quick reading, or an in-depth study?
Followed all the scoped and regular access controls discussions.

> 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 mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20170407/d5ecb83c/attachment.html>