I think the suggestion in the presentation was that it's a tradeoff: C++'s slowness at compilation is what enables it to be both fast at runtime and fast to program (at least when it comes to generic methods; it obviously has other time-sinkholes).
I agree though, I believe it should be possible to get good compilation speed with generic methods, leveraging the simplified syntax etc of Go.
I can't find a comprehensive overview of C++ compiler performance, but this article [1] seems to point towards #includes and duplicate template instantiation. Header file hell is specific to C/C++, but it'll be interesting to see how Go handles generics to tackle the latter issue (or y'know, if they decide not to because of this issue).
Comments
It'd be hard to do worse in compilation speed than C++.
I think the suggestion in the presentation was that it's a tradeoff: C++'s slowness at compilation is what enables it to be both fast at runtime and fast to program (at least when it comes to generic methods; it obviously has other time-sinkholes).
I agree though, I believe it should be possible to get good compilation speed with generic methods, leveraging the simplified syntax etc of Go.
I can't find a comprehensive overview of C++ compiler performance, but this article [1] seems to point towards #includes and duplicate template instantiation. Header file hell is specific to C/C++, but it'll be interesting to see how Go handles generics to tackle the latter issue (or y'know, if they decide not to because of this issue).
[1] http://www.drdobbs.com/cpp/c-compilation-speed/228701711