[swift-evolution] [swift-evolution-announce] [Review] SE-0159: Fix Private Access Levels
spestov at apple.com
Tue Mar 21 02:26:57 CDT 2017
> On Mar 20, 2017, at 11:07 PM, Charlie Monroe via swift-evolution <swift-evolution at swift.org> wrote:
> -1 on this as well for similar reasons. Places where I use fileprivate (aside from what was automatically migrated by Xcode) can be counted on fingers of one or two hands.
> I feel that this proposal is reverting something without offering an alternative solution.
In what situations do you use Swift 3 private where fileprivate is not an acceptable replacement?
>> On Mar 21, 2017, at 3:33 AM, Greg Parker via swift-evolution <swift-evolution at swift.org <mailto:swift-evolution at swift.org>> wrote:
>>> On Mar 20, 2017, at 4:54 PM, Douglas Gregor <dgregor at apple.com <mailto: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 <https://github.com/apple/swift-evolution/blob/master/proposals/0159-fix-private-access-levels.md>
>> -1. I yield the remainder of my time to Drew Crawford who satisfactorily explained my concerns.
>> Greg Parker gparker at apple.com <mailto:gparker at apple.com> Runtime Wrangler
>> swift-evolution mailing list
>> swift-evolution at swift.org <mailto:swift-evolution at swift.org>
> swift-evolution mailing list
> swift-evolution at swift.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-evolution