[swift-evolution] final + lazy + fileprivate modifiers

[Jose Cheyo Jimenez]

> On Feb 19, 2017, at 10:31 PM, David Hart <david at hartbit.com> wrote:
> 
> 
> 
>> On 20 Feb 2017, at 00:52, Tony Arnold via swift-evolution <swift-evolution at swift.org> wrote:
>> 
>> 
>>> On 20 Feb 2017, at 06:25, Jose Cheyo Jimenez via swift-evolution <swift-evolution at swift.org> wrote:
>>> 
>>> We need more examples to make this case. 
>> 
>> How do we provide those examples? This thread has been actively discussed for close to a week now, so it would be good to do something concrete about it. I think Chris’ second suggestion fits my idea of a reasonable “Default” level of privacy when starting out, and fits the model of progressive disclosure as you so excellently pointed out.
>> 
>> Is this something that should go through a proper Proposal? Is someone doing this already? I’d like to help/contribute if it is.
> 
> Chris' second suggestion was dropped by Chris himself after we discussed the disadvantages it adds. I am already working on a proposal to revert to Swift 2's private and it should be ready soon. 

I think this is a good strategy, the alternatives should include keeping scope private but with a different name. Focus on specific code examples and specify how having two overlapping specifiers is harmful.   This is how we were able to reverse only being able to use if let instead of if var 
https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20160125/008145.html



>> thanks,
>> 
>> 
>> Tony
>> 
>> 
>> 
>> ----------
>> Tony Arnold
>> +61 411 268 532
>> http://thecocoabots.com/
>> 
>> ABN: 14831833541
>> 
>> _______________________________________________
>> 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/20170219/0a858a29/attachment.html>