@benjaminencz @NatashaTheRobot My problem has been deducing *which* code is slow to compile, specifically.
-
-
-
@irace@benjaminencz@NatashaTheRobot There's a compiler flag -debug-time-function-bodies that might help. -
@irace@benjaminencz@NatashaTheRobot,@UINT_MIN might also be able to tell you about the new timing stuff he just implemented in nightlies. -
@jckarter@irace@benjaminencz@NatashaTheRobot Mm, that's more for a breakdown of what the compiler is doing. Less actionable.
-
-
-
@benjaminencz@kristinathai Interesting! Is the runtime O(1) vs O(n) ? -
@rayfix@benjaminencz@kristinathai Flatten might be faster since it can precalculate and reserve the final buffer size. -
@jckarter@benjaminencz@kristinathai Oh yes, of course. Any idea what exponential thing is happening in the first case? - View other replies
-
@rayfix@benjaminencz@kristinathai The type checker needs to consider all of the `+` overloads for each +. -
@jckarter@benjaminencz@kristinathai Makes sense! Thanks as always!
-
-
@benjaminencz Swift compiling too slowly? Try pretending it's objc and use library functions instead of language features! -
@benjaminencz@swiftsandbox tradeoff speed compilation vs. execution times in general. -
@benjaminencz@irace I'm seeing long compile times for functions that setup large UIStackView hierarchies (autolayout) and lazy vars. -
@benjaminencz@Freerunnering oh god, why -
@benjaminencz@NatashaTheRobot I believe this is because it has more type information. Should also be fast if you say let array : Array<T> = -
@benjaminencz@NatashaTheRobot I don't like that the compiler can change one's coding style. I see from the replies a fix is in queue.
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.
Benjamin Encz
Bryan Irace
Joe Groff
Jordan Rose
Ray Fix
Sehrgut REACTS!
Marcin Krzyzanowski
Caylan Larson
Árpád Goretity
Ulrik Flænø Damm
David Steuber