[swift-evolution] final + lazy + fileprivate modifiers
Rien at Balancingrock.nl
Fri Feb 17 03:02:22 CST 2017
> On 17 Feb 2017, at 03:36, David Sweeris via swift-evolution <swift-evolution at swift.org> wrote:
>> 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.
> Eh, I've used `private` to keep myself honest in terms of going through some book-keeping functions instead of directly accessing a property.
But is that not an argument to get rid of ‘private’ & ‘fileprivate’?
With great power there comes great responsibility ;-)
> - Dave Sweeris
> swift-evolution mailing list
> swift-evolution at swift.org
More information about the swift-evolution