3 ms·

Direct link to the draft release notes: https://tip.golang.org/doc/go1.12 https://tip.golang.org/doc/go1.12.

weberc2 8y ago
Looks like a very minor release. No changes to the language spec and the changes to the standard library are all marked "minor". The most significant thing is the deprecation of `godoc`'s command-line features in favor of `go doc` (maybe someone with more info could explain the difference between the tools or the rationale for having two similarly named tools and why the CLI features are moving from one and into the other?).
- ainar-g 8y ago
  The rationale is here: https://github.com/golang/go/issues/25443 https://github.com/golang/go/issues/25443. >Now that we have the cmd/go "go doc" CLI for getting documentation, does it make sense for x/tools/cmd/godoc to also have CLI support? >I propose we delete x/tools/cmd/godoc's CLI support and keep it being a web-only tool. Users who want CLI support can use "go doc". Both are shipped with Go releases. It's a deduplication of code and effort.
- tptacek 8y ago
  Changes to the language spec? It's 1.11->1.12, not 1.11->2.0.
  - weberc2 8y ago
    It looks like you're trying to point out an inconsistency with my post, but I'm not seeing it. My observation, "No changes to the language spec" is entirely consistent with my claim, "a very minor release" and your observation, "It's 1.11->1.12, not 1.11->2.0".
    - tptacek 8y ago
      It's literally a minor release. That's what an increment in the numbers on the right of the decimal point means.
      - weberc2 8y ago
        Is this a bad attempt at pedantry? “Minor” WRT version numbers doesn’t mean “boring” or “insignificant”. Go introduced modules in a minor version, for example. Other minor versions cut GC pause times considerably. Others improved compile times a bunch. It’s pretty clear that the aforementioned changes are all more significant/interesting than anything in 1.12.
  - etaoins 8y ago
    Changes to the language spec do not have to be backward incompatible. 8 of the 11 Go 1.x releases have had changes to the language spec.

Looks like a very minor release. No changes to the language spec and the changes to the standard library are all marked "minor". The most significant thing is the deprecation of `godoc`'s command-line features in favor of `go doc` (maybe someone with more info could explain the difference between the tools or the rationale for having two similarly named tools and why the CLI features are moving from one and into the other?).

ainar-g 8y ago
The rationale is here: https://github.com/golang/go/issues/25443 https://github.com/golang/go/issues/25443. >Now that we have the cmd/go "go doc" CLI for getting documentation, does it make sense for x/tools/cmd/godoc to also have CLI support? >I propose we delete x/tools/cmd/godoc's CLI support and keep it being a web-only tool. Users who want CLI support can use "go doc". Both are shipped with Go releases. It's a deduplication of code and effort.
tptacek 8y ago
Changes to the language spec? It's 1.11->1.12, not 1.11->2.0.
- weberc2 8y ago
  It looks like you're trying to point out an inconsistency with my post, but I'm not seeing it. My observation, "No changes to the language spec" is entirely consistent with my claim, "a very minor release" and your observation, "It's 1.11->1.12, not 1.11->2.0".
  - tptacek 8y ago
    It's literally a minor release. That's what an increment in the numbers on the right of the decimal point means.
    - weberc2 8y ago
      Is this a bad attempt at pedantry? “Minor” WRT version numbers doesn’t mean “boring” or “insignificant”. Go introduced modules in a minor version, for example. Other minor versions cut GC pause times considerably. Others improved compile times a bunch. It’s pretty clear that the aforementioned changes are all more significant/interesting than anything in 1.12.
- etaoins 8y ago
  Changes to the language spec do not have to be backward incompatible. 8 of the 11 Go 1.x releases have had changes to the language spec.