[swift-corelibs-dev] NSCoding methods
lukeh at padl.com
Mon Dec 28 15:56:48 CST 2015
> 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.
That is what I meant – and yes I agree.
> In summary - I think perhaps it would be better to start thinking about batching up parts of the NSCoder work and getting it merged before tackling NSValue
Cool, I want to test on Linux first and then reorganise/cleanup the commit history.
More information about the swift-corelibs-dev