3 ms·
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 notic
by gnuvince 11y ago
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.
- dmaz 11y ago> Builds in Go 1.5 will be slower by a factor of about two. https://golang.org/doc/go1.5#performance https://golang.org/doc/go1.5#performance
- deleted 11y ago[deleted]
- chadaustin 11y agoPerhaps 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/5k6016u41oEJ https://groups.google.com/forum/#!msg/golang-dev/6obxRcm-rqc...
- sudhirj 11y agoSlower in the short term while the code remains transpiled from C. Will get faster as the team goes over it a couple times.
- rsc 11y agoYes, this is a good summary.
- semiquaver 11y agoThe 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.