4 ms·
It’s hard to say with any 1.x versions what’ll happen come 2.x
by exdsq 5y ago
It’s hard to say with any 1.x versions what’ll happen come 2.x
- AnimalMuppet 5y agoTrue, but... most languages wouldn't be on version 1.x after the amount of time (and progress) that Go has. Go has a track record by now, of being very careful about breaking things, and providing tools to help fix them when they do. Sure, Go could introduce breaking changes in 2.x. Will they? Track record says "no".
- randomswede 5y agoAs far as I can tell, the only reason for a Go 2 (as opposed to a Go 1.nnnn) is "we introduced a breaking change". Things that were considered "Go 2" are being worked in, as the language evolves, without the need to break previously written code.