4 ms·
Seems like none of them "deliver performance while having fast compilation times", rather that you can pick between fast compilation and high-performance result
by masklinn 8y ago
Seems like none of them "deliver performance while having fast compilation times", rather that you can pick between fast compilation and high-performance result. Which is pretty much the theoretical intention between mainline go[0] and gccgo.
And I will thus restate my original assertion: in 3-5 Go (the mainline compiler) will be nowhere in terms of optimisations. If you want an optimising Go compiler, work on and help with gccgo.
[0] whose maintainers simply don't care for advanced optimisations at the cost of compilation speed
- pjmlp 8y agoOn the the contrary, in some of the mentioned cases it just the difference between debug and release builds. Go's community approach seems to keep being "you are holding it wrong", disregarding experience from other language communities.