Ayaka Nonaka
Spent the morning cutting our Swift compile time by ~3 min. Thanks @irace for the helpful blogpost! http://irace.me/swift-profiling
Nick Lockwood
.@ayanonagon @irace I just tried it. Turns out
{ $0 == "e" || $0== "E" }
takes 100ms more than
{ (c: Character) in c == "e" || c == "E" }
-
-
@ayanonagon@irace to be clear, that's for *every* instance. I had a function in SwiftFormat that has four of those; went from 400ms to 10ms - View other replies
-
@ayanonagon@irace also, it's not a general problem using $0, it's the ||. This is an equally fast option: { "eE".characters.contains($0) } -
@nicklockwood@ayanonagon@irace Hmm, I'm thinking it may have more to do with the Character literals combined with the ||. -
@harlanhaskins@ayanonagon@irace yes, I think the root issue is that too many things are stringLiteralConvertible, so many possible matches
-
-
-
@nicklockwood@ayanonagon@irace@giladronat Interesting; I wonder what the generated SIL/LLVM bytecode/assembly look like -
@andrewcb@ayanonagon@irace@giladronat I'd imagine it's exactly the same (note that we're talking about compile time, not execution time).
-
Harlan Haskins
(((acb)))
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.