> On Mar 17, 2017, at 3:17 PM, Michael LeHew via swift-evolution > <[email protected]> wrote: > > One thing that gets interesting with the scope-restricted visibility of > KeyPaths, is what happens if an fileprivate KeyPath gets leaked out of the > file? That's a scary/maybe useful thing?
I think that, as long as code within the `fileprivate` scope is responsible for passing the KeyPath out, that's an *extremely* useful thing. It essentially lets a privileged scope delegate its access to a less-privileged scope so it can do complex, potentially read-write work on its behalf. Imagine keeping an instance variable private, but allowing a serialization framework to access it through a key path; that'd be pretty handy. -- Brent Royal-Gordon Architechies
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
