Re:Introduction to Go 1.1
by mseepgood on Tuesday March 26, 2013 @03:41AM
(#5441816)
It's not released yet, this is just a preliminary document. There are still open issues for Go 1.1: http://swtch.com/~rsc/go11.html
And I guess there will be a RC first.
[ Parent
| on HN ]
Is there any ETA on the release or is it just a case of "when it's finished"?
I'm about to start a largish project in Go and I'm thinking I'd rather start in Go 1.1 rather than worry about upgrading and testing the project mid-development.
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.
It'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 :)
See http://golang.org/doc/go1compat.html for details on compatibility.
It is a guarantee. I promise, you won't have to change any of your code when updating from 1.0 to 1.1.
True.
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.
hg tip is very stable. If you want to start your project on Go 1.1 then just checkout the tip and use it.
You can upgrade to Go1.1 when it's released with very minor changes when it's released.
Re:Introduction to Go 1.1
by georgemcbay on Tuesday March 26, 2013 @05:11PM
(#5446105)
Just wanted to chime in confirming that in my experience for development work you might as well just use Go tip. It is quite stable and in many situations (eg. you're deploying to ARM, or 32-bit targets) is far more stable/usable than 1.0.3 despite not being an official release.
If you do run from tip, please check the build dashboard: http://build.golang.org/ We make no guarantees about the stability of tip, which should be obvious but I feel compelled to point it out anyway.