@owensd Thanks for updating.
@daringfireball At this rate I’m expecting some Kubrick news by the end of the week.
@jckarter @pathofshrines Awesome, thanks.
@jckarter Because KVO checks are relaxed or because addresses of ivars are handled differently?
Is This My Interface or Yours?: https://t.co/BCIf3wLRsK #mjtsaiblog
1980s Apple Ads: https://t.co/4Z70HQlHoY #mjtsaiblog
Data Locality and STL vs. Swift: https://t.co/SLbDnlhy6D #mjtsaiblog
1Password Command-line Tool Public Beta: https://t.co/yhlT6Xs1w4 #mjtsaiblog
Swift and KVO Context Variables: https://t.co/reMlho2TUF #mjtsaiblog
@jckarter @owensd Yeah, I would have expected it to inline access to start index, etc., instead of calling through a witness table.
@owensd Your code seems too simple to be wrong. A quick look in Instruments seems to show a lot of protocol overhead…
@owensd Reallocating seems like a good guess. Why would you need a lot of ARC for Ints?
@owensd LL is not that surprising; I assume there’s ref-counting overhead. But two orders of magnitude slower for an array of Int?
@owensd Wow, I wonder why the Swift numbers are so bad.
@stuwillis Yes, still using for archives of projects and OS installations.