Still better than exposing to any subclass implementation or direct external 
access IMHO.

Sent from my iPhone. Erroneous words are a feature, not a typo.

> On 1 Dec 2016, at 07:40, Jean-Daniel <d...@xenonium.com> wrote:
> 
> If you add a typeprivate accessor,  it means you expose your internal details 
> to all extensions and so breaks encapsulation.
_______________________________________________
swift-evolution mailing list
swift-evolution@swift.org
https://lists.swift.org/mailman/listinfo/swift-evolution

Reply via email to