-
-
@wilshipley@phink0 [fast] Is this something you expect or something you measured? My measurements to date almost exclusively show opposite.0 replies 0 retweets 2 likes -
@mpweiher@wilshipley What am I doing wrong? Swift 6x slower than very naive ObjC filter. XCode7.3.1, [-O], iPhone5Spic.twitter.com/U20uvcRPFj
0 replies 3 retweets 9 likes -
@phink0@wilshipley That looks about smack in the middle of the relative slowdowns I have been seeing.0 replies 0 retweets 1 like -
@mpweiher@phink0@wilshipley That’s very interesting. Have you tried profiling it? Bridging overhead?0 replies 0 retweets 0 likes -
@mjtsai@mpweiher@wilshipley Here's the profile (and for completeness the ObjC simple/naive/ugly filter category)pic.twitter.com/lbeIS8sEg8
0 replies 0 retweets 1 like -
@phink0@mpweiher@wilshipley The Foundation -hasPrefix: does an exact compare; maybe Swift stdlib one does a fancy Unicode compare.0 replies 0 retweets 0 likes -
@mjtsai@phink0@mpweiher@wilshipley Yeah. Some Unicode operations are also implemented naively and make unnecessary extra copies.0 replies 0 retweets 2 likes -
@mjtsai@phink0@mpweiher@wilshipley Would be interesting to compare with x.utf16.startsWith(y.utf16) to see if that's the case.0 replies 0 retweets 0 likes -
@jckarter@phink0@mpweiher@wilshipley In XCTest, I found ($0 as NSString) only 5% faster and $0.utf16.startswith 34% faster.0 replies 0 retweets 2 likes
@mjtsai @phink0 @mpweiher @wilshipley Does x.lazy.filter to avoid the intermediate array construction improve more?
-
@jckarter@phink0@mpweiher@wilshipley About 10%.0 replies 0 retweets 1 like
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
Wil Shipley
Marcel Weiher
Marco Scheurer
Michael Tsai
Joe Groff