Are we too early for "Go-2 considered harmful" jokes?
There is always the possibility that a go fix tool makes a transition to version 2 super simple.
The maintainers have already publicly stated that this will be the case. They used python 2 to 3 as an example of what they're NOT going to do.
Awesome. Does anybody here know where this discussion happened, for further reference?
I believe the "official" start of the discussion was on the Go blog [1].
Indeed, thanks.
Here is the relevant part from it:
> Go 2 must also bring along all the existing Go 1 source code. We must not split the Go ecosystem. Mixed programs, in which packages written in Go 2 import packages written in Go 1 and vice versa, must work effortlessly during a transition period of multiple years. We'll have to figure out exactly how to do that; automated tooling like go fix will certainly play a part.
Running old code and having it "just work" is something I really love with go. I hope go-2 new features won't come at the cost of breaking old code.