On Tue, Sep 27, 2016, at 01:34 AM, Jeremy Pereira via swift-evolution wrote: > As for dropping file private, why? You don’t have to use it if you don’t > want to, so it’s not hurting you. On the other hand, I can use it when I > deem it to be the right thing to do. I'll politely disagree and point out you *must* use fileprivate in order to get what it provides. It's unavoidable in that sense. As the access control change has been implemented for what only can be described in a number of weeks, it's disappointing that a feature I used to great effect in prior versions of Swift has already been relegated to "if you don't like the name, don't use it." Sincerely, Zachary Waldowski [email protected] _______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
Re: [swift-evolution] class/struct inner member access scope classifier
Zach Waldowski via swift-evolution Tue, 27 Sep 2016 06:21:14 -0700
- [swift-evolution] class/struct... Ted F.A. van Gaalen via swift-evolution
- Re: [swift-evolution] cla... Nevin Brackett-Rozinsky via swift-evolution
- Re: [swift-evolution] cla... Jeremy Pereira via swift-evolution
- Re: [swift-evolution]... Zach Waldowski via swift-evolution
- Re: [swift-evolut... Shawn Erickson via swift-evolution
- Re: [swift-evolut... Jeremy Pereira via swift-evolution
- Re: [swift-ev... Nevin Brackett-Rozinsky via swift-evolution
- Re: [swi... Sean Heber via swift-evolution
- Re: ... Jay Abbott via swift-evolution
- Re: [swift-evolution]... Ted F.A. van Gaalen via swift-evolution
