> On 27 May 2016, at 04:44, Austin Zheng via swift-evolution > <[email protected]> wrote: > > My personal preference would be to honor access control, and consider ser/de > separately (especially since there are so many other possible considerations > for that feature). Access control in Swift isn't just another safety feature, > it's also a boundary for things like the optimizer. > > To be honest, I expect the first big use of a feature like this to be turning > JSON or XML received from a network call into model objects for an app. There > are quite a few Objective-C libraries that use KVC to implement this > functionality.
That's what I want to use it for and I'm fairly sure we need access to private properties for that. _______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
