The below is an off-site archive of all tweets posted by @mjtsai ever

September 6th, 2017

@daringfireball At this rate I’m expecting some Kubrick news by the end of the week.

via Tweetbot for Mac

@jckarter Because KVO checks are relaxed or because addresses of ivars are handled differently?

via Tweetbot for Mac in reply to jckarter

Is This My Interface or Yours?: https://t.co/BCIf3wLRsK #mjtsaiblog

via IFTTT

Data Locality and STL vs. Swift: https://t.co/SLbDnlhy6D #mjtsaiblog

via IFTTT

1Password Command-line Tool Public Beta: https://t.co/yhlT6Xs1w4 #mjtsaiblog

via IFTTT

Swift and KVO Context Variables: https://t.co/reMlho2TUF #mjtsaiblog

via IFTTT

@jckarter @owensd Any way to give it a hint, given that it already knows it’s an Array<Int>?

via Tweetbot for Mac in reply to jckarter

@jckarter @owensd Yeah, I would have expected it to inline access to start index, etc., instead of calling through a witness table.

via Tweetbot for Mac in reply to jckarter

@jckarter @owensd Interesting…although that doesn’t seem to be what’s slowing this down.

via Tweetbot for Mac in reply to jckarter

@owensd Your code seems too simple to be wrong. A quick look in Instruments seems to show a lot of protocol overhead…

via Tweetbot for Mac in reply to owensd

@owensd Reallocating seems like a good guess. Why would you need a lot of ARC for Ints?

via Tweetbot for Mac in reply to owensd

@rowanxmas @owensd Pretty sure Swift does’t do that.

via Tweetbot for Mac in reply to rowanxmas

@owensd LL is not that surprising; I assume there’s ref-counting overhead. But two orders of magnitude slower for an array of Int?

via Tweetbot for Mac in reply to owensd

@owensd Wow, I wonder why the Swift numbers are so bad.

via Tweetbot for Mac in reply to owensd

@stuwillis Yes, still using for archives of projects and OS installations.

via Tweetbot for Mac in reply to stuwillis