Twitter | Search | |
David Smith
btw, NSArray and CFArrayCreate* will now return _NSArrayI and _NSArrayM instances on iOS/watchOS/tvOS as they have for some time on macOS.
Reply Retweet Like More
David Smith 13 Jun 16
Replying to @Catfish_Man
In general, shouldn’t change anything except for better performance (faster + less mem used) and different name in NSLog output
Reply Retweet Like
David Smith 13 Jun 16
Replying to @thecasserpillar
I know right? I guess they’re too attached to the branding there 😂
Reply Retweet Like
Paul Haddad 13 Jun 16
Replying to @Catfish_Man
favorite iOS/macOS 10/.12 performance tweak?
Reply Retweet Like
David Smith 13 Jun 16
Replying to @tapbot_paul
os_unfair_lock by a light year. In F/CF land though, there’s a lot… hm… * CF_IS_OBJC is way faster (used in bridging)
Reply Retweet Like
Joefrey Kibuule, MD 13 Jun 16
I love when you make Foundation faster so I don’t have to do anything. ;)
Reply Retweet Like
Robin Kunde 13 Jun 16
Replying to @Catfish_Man
can you talk about why that's happening only now?
Reply Retweet Like
David Smith 13 Jun 16
Replying to @tapbot_paul
* _NSDictionaryM combines buffers for 33-50% fewer mallocs * -retain/isEqual/hash on CF types calls new _CFNonObjC*
Reply Retweet Like
✾ 13 Jun 16
I don't want to return to the iPad launches and the Increasingly Inaccurately Names iPhone OS era.
Reply Retweet Like
David Smith 13 Jun 16
Replying to @tapbot_paul
* CFRetain calls objc_retain instead of -retain * Collections call objc_retain instead of CFRetain * Silly memcpy tricks
Reply Retweet Like
David Smith 13 Jun 16
Replying to @robinkunde
they used to cause perf regressions but saved memory. We fixed the perf regressions.
Reply Retweet Like
Madelinemas TV 13 Jun 16
the App Store was a mistake
Reply Retweet Like
✾ 13 Jun 16
eating Doritos: also a mistake
Reply Retweet Like
David Smith 13 Jun 16
Replying to @tapbot_paul
remind me to dig up some more later. Out and about now.
Reply Retweet Like
Paul Haddad 13 Jun 16
Replying to @Catfish_Man
on the I/M variants, is I significantly faster/smaller? Meaning it might make sense to copy an NSMutableArray after creation?
Reply Retweet Like
David Smith 13 Jun 16
Replying to @tapbot_paul
_NSArrayI is a single allocation. _NSArrayM has a pointer to a separate buffer.
Reply Retweet Like
David Smith 13 Jun 16
Replying to @Catfish_Man
(Though as mentioned in the Foundation relnotes this means that CF calls are an indirection overhead vs ObjC calls instead of vice versa.)
Reply Retweet Like
David Smith 13 Jun 16
Replying to @tapbot_paul
. oh, plist encoding/decoding should be a bunch faster due to various changes, but I’ve had trouble getting reliable numbers.
Reply Retweet Like