4 ms·
It's "when it's finished", but you can expect it in the near future. Go 1.1 is strongly backward compatible. You can start working on a large project right now
by dsymonds 14y ago
It's "when it's finished", but you can expect it in the near future.
Go 1.1 is strongly backward compatible. You can start working on a large project right now with Go 1.0.3 and it'll work just as correctly under Go 1.1.
- laumars 14y agoIt's the term "strongly" that concerns me as that's not really a guarantee. However I think I will take your advice and start development on it regardless (if I've written it correctly, then any breaking changes will be confined to their respective module so fixing them shouldn't be much of an ordeal). Thanks for the feedback :)
- dchest 14y agoSee http://golang.org/doc/go1compat.html http://golang.org/doc/go1compat.html for details on compatibility.
- enneff 14y agoIt is a guarantee. I promise, you won't have to change any of your code when updating from 1.0 to 1.1.
- ithkuil 14y agoTrue. Except if you used ListenUnixgram returned and couldn't use type inference for storing it's return value. Go1.0 returns UDPConn, which will be renamed as UnixConn. This is a clear API bug, and it's the only exception to the backward compatibility rule.