[swift-evolution] [Review] SE-0159: Fix Private Access Levels
swift at lng.la
Thu Mar 23 19:52:10 CDT 2017
Given that this is such a divisive issue, I'd like to see a revised version of this proposal that renames fileprivate back to private but maintains scoped access control under a different name like "scoped", as has been suggested. That seems like the best compromise -- those that want scoped access control can continue to use it, and those that don't can go back to using private.
> 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:
> Reviews are an important part of the Swift evolution process. All reviews should be sent to the swift-evolution mailing list at
> 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:
> 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
> Thank you,
> Review Manager
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-evolution