We will see how this will fare one way or the other in say 10-15 years.

Sent from my iPhone

> On 15 Oct 2016, at 14:43, Jean-Daniel via swift-evolution 
> <swift-evolution@swift.org> wrote:
> 
> 
>> Le 13 oct. 2016 à 23:27, Ted F.A. van Gaalen <tedvgios...@gmail.com> a écrit 
>> :
>> 
>> Please do NOT drop the current distinction between *private* and 
>> *fileprivate*
>> as it is now in Swift 3
>> It is needed for correct OOP.  
>> 
> 
> That argument don’t apply for a language where you can structure your code in 
> extensions as in Swift.
> 
> 
> _______________________________________________
> swift-evolution mailing list
> swift-evolution@swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
_______________________________________________
swift-evolution mailing list
swift-evolution@swift.org
https://lists.swift.org/mailman/listinfo/swift-evolution

Reply via email to