3 ms·
There is an amount of time spent compiling which has a qualitative effect on my programming. I start to feel it around ten seconds, definitely by thirty; three
by samatman 6y ago
There is an amount of time spent compiling which has a qualitative effect on my programming. I start to feel it around ten seconds, definitely by thirty; three minutes is way over the line.
I start to be reluctant to make small tweaks. I want to program in 'blocks', time compiling with bathroom breaks. My frame is just wrecked, and I'm fairly convinced that code quality suffers from this.
I like what Zig is doing, by taking such care to keep unoptimized builds as fast as possible. Release builds can run overnight for all I care, I'm fine with taking arbitrary amounts of time to get the fastest end product I can have.
But I firmly believe that a language which can't give me a build in a handful of seconds is missing out, and it's a real pity Rust is in that category.
It's possible that a language with type inference and a borrow checker simply must have slow compile times, that it's inherent. I doubt that somehow, though I concede that one-pass compiling a la Turbo Pascal is likely impossible.
- darksaints 6y agoAre those your compile times with incremental compilation?
- samatman 6y agoThose are real compile times I've experienced, the post is about what it feels like for compiling to take "too long" and approximately what "too long" is. Rather than what it's like to use a particular compiler on a specific project, at this moment in time.