>as much as what Go is compiled into, which hasn't changed all that much as far as I know
What are you talking about? Go code generation is getting better all the time.
What are you talking about? Go code generation is getting better all the time.
That said, I took the original statement about Go switching from Co to Go to indicate there's been major changes in the compiler, so it would be interesting to see more recent results, not that the change itself necessarily was responsible for major speed improvements, but they could very well have assumed the compiler change would have had a larger affect on the resulting binary depending on their understanding of the Go toolchain.