> On Mar 20, 2017, at 11:07 PM, Charlie Monroe via swift-evolution > <swift-evolution@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? Slava > >> On Mar 21, 2017, at 3:33 AM, Greg Parker via swift-evolution >> <swift-evolution@swift.org <mailto:swift-evolution@swift.org>> wrote: >> >> >>> On Mar 20, 2017, at 4:54 PM, Douglas Gregor <dgre...@apple.com >>> <mailto:dgre...@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 gpar...@apple.com <mailto:gpar...@apple.com> Runtime >> Wrangler >> >> >> _______________________________________________ >> swift-evolution mailing list >> swift-evolution@swift.org <mailto:swift-evolution@swift.org> >> https://lists.swift.org/mailman/listinfo/swift-evolution > > _______________________________________________ > swift-evolution mailing list > swift-evolution@swift.org > https://lists.swift.org/mailman/listinfo/swift-evolution
_______________________________________________ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution
