Bryan Irace

@irace @eridius Did this impact incremental builds, or only clean builds? I'd hope incremental builds would avoid rechecking.

@jckarter @eridius Definitely impacted incremental builds as well.

@irace @eridius cc @UINT_MIN, is that expected?

@jckarter @irace @eridius Incremental builds aren't incremental /within/ a file—currently no way to know what changed.

@jckarter @irace After reading your blog post, though, I'm also not sure why the same fn is getting recompiled. Can we see the project?

@UINT_MIN @jckarter I don’t think I can share it, unfortunately. if it helps, these were each one-line properties (one computed, two lazy).

. @irace someone could make a nice tool that you could pipe the xcodebuild output through and give you some useful highlights

@orta That someone may or may not be @brianmichel

@irace (small comment: you can combine both commands by doing `xcodebuild -workspace […] -scheme […] clean build | […]`)

@irace I tried this, but I have a compiler error: unknown argument: '-debug-time-function-bodies' Any guess what’s wrong here?

@milancermak You need the `frontend` argument as well.

@irace @Freerunnering @eridius I buy that array appending is slow _at runtime_, but why does it *compile* for more than 3 seconds?

@H2CO3_iOS @irace @Freerunnering Type-checking. It’s considering all possible array types for all 3 literals that might possibly work.

@eridius @irace @Freerunnering Ouch. Shouldn't it just bail if they are not all equal?

@irace @eridius this post is GENIUS! I found 4 functions that take more than 6000ms! Thanks a lot

@vittorio_monaco @irace Bug reports I can dupe?

@kluivers @irace well, the slowest func (6530ms) was appending 3 arrays with the + operator... Noob mistake I guess?