4 ms·

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 http://swtch.com/~rsc/go11.h

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 http://swtch.com/~rsc/go11.html And I guess there will be a RC first.

laumars 14y ago
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.
- 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 ago
    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 :)
    - dchest 14y ago
      See http://golang.org/doc/go1compat.html http://golang.org/doc/go1compat.html for details on compatibility.
    - enneff 14y ago
      It 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 ago
        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.
- jesstaa 14y ago
  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.
  - georgemcbay 14y ago
    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.
    - enneff 14y ago
      If you do run from tip, please check the build dashboard: http://build.golang.org/ 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.

laumars 14y ago

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.

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 ago
  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 :)
  - dchest 14y ago
    See http://golang.org/doc/go1compat.html http://golang.org/doc/go1compat.html for details on compatibility.
  - enneff 14y ago
    It 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 ago
      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.
jesstaa 14y ago
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.
- georgemcbay 14y ago
  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.
  - enneff 14y ago
    If you do run from tip, please check the build dashboard: http://build.golang.org/ 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.