@phink0 @jckarter @mpweiher Transitions aren’t fun, but I mostly find Swift more pleasant and like that it tries to do Unicode right.
Making Paw Extensible With JavaScript Core: mjtsai.com/blog/2016/05/2… #mjtsaiblog
iTunes 12.4 Applies Song Ratings to Albums and Destroys Smart Playlists: mjtsai.com/blog/2016/05/2… #mjtsaiblog
Opening Files and Never Closing Them: mjtsai.com/blog/2016/05/2… #mjtsaiblog
Another “Dynamic Swift” update showing how to call a method on an Any and implement a responder chain: mjtsai.com/blog/2016/05/2… #mjtsaiblog
@jckarter @mpweiher @phink0 @wilshipley I’ve only been timing different Swift versions vs. Marco’s original. Didn’t test Obj-C.
@mpweiher @jckarter @phink0 @wilshipley You can see in Hopper that it’s only passing NSAnchoredSearch.
@mpweiher @jckarter @phink0 @wilshipley If you look at the code, Swift is using kCFCompareNonliteral and NSString is not.
@jckarter @phink0 @mpweiher @wilshipley About 10%.
@jckarter @phink0 @mpweiher @wilshipley In XCTest, I found ($0 as NSString) only 5% faster and $0.utf16.startswith 34% faster.
@phink0 @mpweiher @wilshipley The Foundation -hasPrefix: does an exact compare; maybe Swift stdlib one does a fancy Unicode compare.
@mpweiher @phink0 @wilshipley That’s very interesting. Have you tried profiling it? Bridging overhead?