Re:Go 1.5 is released
by gnuvince on Wednesday August 19, 2015 @01:51PM
(#10087229)
How has this affected compile speeds? Go proponents often tout the speed at which it compiles code as an important feature, so I wonder if there's been a noticeable regression.
[ Parent
| on HN ]
Slower in the short term while the code remains transpiled from C. Will get faster as the team goes over it a couple times.
Yes, this is a good summary.
> Builds in Go 1.5 will be slower by a factor of about two.
Re:Go 1.5 is released
by semiquaver on Wednesday August 19, 2015 @05:26PM
(#10088623)
The small increase in build times doesn't bother me at all when I'm generating a binary, but unfortunately it's very noticeable and irritating when using tools like vim-go or syntastic which type-check/lint/gofmt your code. Using these now causes vim to be unresponsive for up to a second every time I save, whereas the delay used to be insignificant.
> which type-check/lint/gofmt your code
Those tools do not use the Go compiler. They're using go/ast or go/types. So the translation of gc from C to Go can't have affected them.
They also build the source file, which is indeed much slower, to about 2x.
Re:Go 1.5 is released
by chadaustin on Wednesday August 19, 2015 @02:00PM
(#10087282)
Perhaps things have improved since then, but this thread indicates build times will regress a little:
https://groups.google.com/forum/#!msg/golang-dev/6obxRcm-rqc...