Go 1.21, released last week, mentions that it continues (and even enhances) the compatibility promises of Go 1 . Still, one wonders if there will be a future "Go 2" release that breaks compatibility with existing Go 1.x programs.
Yesterday, Russ Cox (rsc), the technical leader of the Go development team, published a blog detailing the improvements to Go's backward compatibility and answering the above questions.
rsc responded that the answer was never. If by "broken" you meant no compatibility with older versions, no support for compiling older programs, Go 2 would never have appeared . Judging from the major overhaul of Go 1 that began in 2017, Go 2 has in fact existed for a long time.
The so-called Go 2 is not a single major update, but gradually reaches "Go 2.0" through "incremental updates".
He said that in the future, not only will the compatibility between Go 2 and Go 1 not be destroyed, but the compatibility between the two will be actively improved. The team considers prioritizing compatibility as the most important design decision made for Go 1.
As a result, developers will see a ton of exciting new changes over the next few years, done in a careful, compatible manner.
For more information see: