4 ms·
I recently wrote a tool to report Swift block compile times, since this kind of thing can be unpredictable. At Hipmunk we run it every night to find out how we
by stevejohnson 10y ago
I recently wrote a tool to report Swift block compile times, since this kind of thing can be unpredictable. At Hipmunk we run it every night to find out how we can make our builds faster.
Another common culprit of slow compile times is usage of lazy var.
https://github.com/irskep/swift_compile_times_parser https://github.com/irskep/swift_compile_times_parser
- jopamer 10y agoThanks, Steve! I'm well aware of the type checker's problems with 'lazy', and it's something I hope to address soon.
- stevejohnson 10y agoWhile you're here, I should say: first, thanks for your work, and second, it would be nice if the compiler could log the timing data in a consolidated form so my script wouldn't be necessary. :-) Regex-parsing and aggregating a bunch of log lines seems dicey.
- jopamer 10y agoUnfortunately, debug-time-function-bodies isn't an "officially" supported flag, so improving it isn't a high priority right now. ...That said, we'd be more than happy to take improvement PRs in this area, if you're feeling up for it!
- rudedogg 10y agoI'm going to have to try this tomorrow. My builds seem to have gotten slower in the past week or two; hopefully I find something. Thanks!