[swift-evolution] class/struct inner member access scope classifier

Shawn Erickson shawnce at gmail.com
Tue Sep 27 10:04:34 CDT 2016

If coming from that perspective if has only changed name to fileprivate
from private and you can then ignore private if you don't find it useful.
If anything it more clearly states in common language your intent then the
old naming (especial compared to other languages).

On Tue, Sep 27, 2016 at 6:20 AM Zach Waldowski via swift-evolution <
swift-evolution at swift.org> wrote:

> 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
>   zach at waldowski.me
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160927/7cf3d8fa/attachment.html>

More information about the swift-evolution mailing list