[swift-evolution] final + lazy + fileprivate modifiers

Matt Whiteside mwhiteside.dev at gmail.com
Sat Feb 18 15:30:12 CST 2017

> On Feb 16, 2017, at 14:34, Slava Pestov via swift-evolution <swift-evolution at swift.org> wrote:
> While we’re bikeshedding, I’m going to add my two cents. Hold on to your hat because this might be controversial here.
> I think both ‘private’ and ‘fileprivate’ are unnecessary complications that only serve to clutter the language.
> It would make a lot more sense to just have internal and public only. No private, no fileprivate, no lineprivate, no protected. It’s all silly.
> Slava

I am behind this idea too.  The access control modifiers seem like mostly a distraction from more interesting considerations.  If they are causing big headaches in the implementation, I wouldn’t mind if they were cut down to just internal and public.


More information about the swift-evolution mailing list