[swift-evolution] [Review] SE-0159: Fix Private Access Levels
voidref at me.com
Thu Mar 23 22:37:32 CDT 2017
What is your evaluation of the proposal?
Strongly in favor: +1
Is the problem being addressed significant enough to warrant a change to Swift?
Having to deal with the fallout from the original proposal every day, I would say yes.
Does this proposal fit well with the feel and direction of Swift?
For the long term evolution and philosophy of the language, I believe this is a positive change.
If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?
I’m not sure a comparison is apt in this case, the point of Swift is to be better, you can’t be better and be the same.
How much effort did you put into your review? A glance, a quick reading, or an in-depth study?
Merely personal anecdotal experience with some large codebases that have taken to de facto writing `fileprivate` for everything as the current `private` appears to be too persnickety to use in the general case.
swift-evolution mailing list
swift-evolution at swift.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-evolution