3 ms·

Any idea what causes this increase? I'm surprised as I understood fast compilation times to be one of Go's major strengths.

• peterwaller 11y ago
  The increase was caused during 1.4->1.5 by translating the whole compiler toolchain from C to Go. The core devs focussed on correctness over performance on the first pass. They clawed back a lot of the performance already, and though it is slower than it used to be, it isn't at all bad compared with C++ and other languages I've used.
• masklinn 11y ago
  The compiler was convert/rewritten from C to Go.
• dilap 11y ago
  I'm a little sad about the slower compiler speed to, though it's still lightyears better than C++. But for my project it's juuust long enough that not having status printed while compiling feels pretty annoying. If they just printed out each file as it was compiled, it would go back to feeling lightning fast. :) (Maybe there's a way to do this?)
  • ustolemyname 11y ago
    go build -x will print the subcommands as it executes them, is that what you are looking for?
    • dilap 11y ago
      boom! that does it, thanks. (well actually what i reallly want is in between -- just each file name as it compiled, in a pretty list that gives me something to look at while waiting for the compile. but this is 𝞊 away.)