[swift-evolution] private & fileprivate

[ted van gaalen]

in 10-15 years compilers/interpreters are merged and update themselves as AI.
so we can tell in human language what an app should do :o)

@Jean: can you explain that about extensions in this context (oop) ?

TedvG


ted van gaalen

> On 15 Oct 2016, at 21:44, Goffredo Marocchi <panajev at gmail.com> wrote:
> 
> 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 at swift.org> wrote:
>> 
>> 
>>> Le 13 oct. 2016 à 23:27, Ted F.A. van Gaalen <tedvgiosdev at 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 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/20161015/38c8781f/attachment.html>