[swift-evolution] Swift evolution proposal: introduce typeprivate access control level

João David david.joao at gmail.com
Thu Dec 1 02:55:45 CST 2016

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 <dev at xenonium.com> wrote:
> If you add a typeprivate accessor,  it means you expose your internal details to all extensions and so breaks encapsulation.

More information about the swift-evolution mailing list