[swift-evolution] [Review] SE-0159: Fix Private Access Levels
Jose Cheyo Jimenez
cheyo at masters3d.com
Mon Mar 20 20:20:59 CDT 2017
> What is your evaluation of the proposal?
> Is the problem being addressed significant enough to warrant a change to Swift?
Yes. Making scope private be the soft default (private) created much confusion . The incredible overlap that this change created for fileprivate and private is actively harmful. Reverting this now will allow a more powerful scope access to be added much later in conjunction with a comprehensive module system.
> 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?
Swift 1 and 2.
Easy to understand.
Worked great with extensions.
> How much effort did you put into your review? A glance, a quick reading, or an in-depth study?
Participated extensibly on the conversations leading to the proposal.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-evolution