That's a nice workaround - but nice in a sense that that it's a hack, not a solution IMHO.
> On May 30, 2016, at 6:49 AM, Callionica (Swift) via swift-evolution > <swift-evolution@swift.org> wrote: > > I've written up how to provide protected access control for Swift code today > here: > > http://www.callionica.com/developer/#swift-protected > <http://www.callionica.com/developer/#swift-protected> > > No compiler changes necessary for this technique and it distinguishes between > methods that can only be overridden and methods that can be both called and > overridden. > > _______________________________________________ > 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
