[swift-corelibs-dev] NSCoding methods

[Luke Howard]

> On 29 Dec 2015, at 3:01 AM, Philippe Hausler <phausler at apple.com> wrote:
> 
> Not certain what you mean there; each NSValue is just a identity of a key in a dictionary to a NSConcreteValue that the methods forward to? That would mean that each method call would be a dictionary lookup… that does not sound scalable from a performance standpoint.

Although didn’t NSObject do something similar for managing the retain count when it didn’t fit inline? I’m too lazy to go look it up...

— Luke