[irfansharif]

From Go's 1.0 compatibility guarantee[0]:

> It is intended that programs written to the Go 1 specification will continue to compile and run correctly, unchanged, over the lifetime of that specification. [...] Go programs that work today should continue to work even as future "point" releases of Go 1 arise (Go 1.1, Go 1.2, etc.).

I've found this to be upheld in practice, especially so for the standard library. I have yet to come across a case where I was concerned with which "version" of the standard library some project was written against. Are you perhaps talking about non-stdlib packages?

[0]: https://golang.org/doc/go1compat

[ovao]

My experience has been the same, so it’s hard to understand where shawn is coming from. There have been impressively few breaking changes to the Go standard library since 1.0.

Even when bringing in a number of third-party packages, the only trouble I’ve had building Go projects has been in Windows (which is often treated by Gophers as a second-class platform).