4 ms·

There isn't any evidence to suggest this. Slow compilation speed is mostly a consequence of priorities. See https://nikic.github.io/2020/05/10/Make-LLVM-fast-ag

There isn't any evidence to suggest this. Slow compilation speed is mostly a consequence of priorities. See https://nikic.github.io/2020/05/10/Make-LLVM-fast-again.html https://nikic.github.io/2020/05/10/Make-LLVM-fast-again.html and https://www.reddit.com/r/haskell/comments/45q90s/is_anything_being_done_to_remedy_the_soul/czzmbt1/ https://www.reddit.com/r/haskell/comments/45q90s/is_anything.... Sure, there are some language features that can make optimizations pathological complex, but for the most part if compilation speed isn't continuously tracked and strictly enforced against new changes, you inevitably regress into a slower compiler. For instance, the Go community is highly sensitive to compilation speed. Although the Go compiler is SSA-based like LLVM, it's very selective about the optimizations applied. The Go compiler tracks and benchmarks each phase of the compiler release-to-release to identify major regressions.

atombender 6y ago
Are benchmarks posted publicly anywhere, like Rust does with their compiler?
- smnscu 6y ago
  It would be weird if that was not the case, as Go and all its bells and whistles are open source. I found this after a quick search (clicking around will send you to the source code): https://godoc.org/golang.org/x/tools/cmd/compilebench https://godoc.org/golang.org/x/tools/cmd/compilebench edit: Ooh, that's nice, I did not know about that, thanks for sharing (especially useful as I'm transitioning to Rust after 10yrs of Go).
  - atombender 6y ago
    Sorry, I mean a public web page for viewing results with charts and tables, like Rust has [1]. [1] https://perf.rust-lang.org/ https://perf.rust-lang.org/
cies 6y ago
Priorities exactly. And these priorities are not only down to the compiler implementation, but also the language design. I'd argue that Rust being much slower to compile than Go has reasons from both sides, and hence will probably never be as fast as Go to compile.
- kaba0 6y ago
  Rust’s compiler does way more work than Go’s - it is not priorities..

atombender 6y ago

Are benchmarks posted publicly anywhere, like Rust does with their compiler?

smnscu 6y ago
It would be weird if that was not the case, as Go and all its bells and whistles are open source. I found this after a quick search (clicking around will send you to the source code): https://godoc.org/golang.org/x/tools/cmd/compilebench https://godoc.org/golang.org/x/tools/cmd/compilebench edit: Ooh, that's nice, I did not know about that, thanks for sharing (especially useful as I'm transitioning to Rust after 10yrs of Go).
- atombender 6y ago
  Sorry, I mean a public web page for viewing results with charts and tables, like Rust has [1]. [1] https://perf.rust-lang.org/ https://perf.rust-lang.org/

cies 6y ago

Priorities exactly. And these priorities are not only down to the compiler implementation, but also the language design. I'd argue that Rust being much slower to compile than Go has reasons from both sides, and hence will probably never be as fast as Go to compile.

kaba0 6y ago
Rust’s compiler does way more work than Go’s - it is not priorities..