[swift-evolution] [Idea] Further directions for id-as-Any
brent at architechies.com
Tue Sep 6 16:45:26 CDT 2016
> On Sep 6, 2016, at 10:02 AM, Will Field-Thompson <will.a.ft at gmail.com> wrote:
> I would rather see a Swift-centric rethinking of serialization than having the runtime dynamically register Objective-C classes anytime I want to serialize something. Plus, that seems like it's leaving Linux users out in the cold for serialization — although I'm primarily a macOS/iOS user, so maybe there's something I don't know about the corelibs Foundation implementation.
I do hope that it will *also* become possible to access a Swift type in pure Swift given a name and a protocol it conforms to, which would allow Corelibs Foundation to also support NSCoding on value types. But that's a separate issue from improving Objective-C bridging.
More information about the swift-evolution