News for hackers. Stuff that matters.
Re:Go Home Swift Compiler, You’re Drunk by stevejohnson on Tuesday April 26, 2016 @08:45PM (#11577017)
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

Re:Go Home Swift Compiler, You’re Drunk by jopamer on Tuesday April 26, 2016 @08:57PM (#11577057)
Thanks, Steve! I'm well aware of the type checker's problems with 'lazy', and it's something I hope to address soon.
Re:Go Home Swift Compiler, You’re Drunk by stevejohnson on Tuesday April 26, 2016 @09:00PM (#11577075)
While 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.
Re:Go Home Swift Compiler, You’re Drunk by jopamer on Tuesday April 26, 2016 @09:49PM (#11577274)
Unfortunately, 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!

Re:Go Home Swift Compiler, You’re Drunk by rudedogg on Wednesday April 27, 2016 @01:13AM (#11577956)
I'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!