> 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

Reply via email to