Hello Gophers,
We are fast approaching our development freeze (starting beginning of May, 2019).
As you may remember, we introduced a new process for Go 2 related language changes in our blog post Go 2, here we come!. We started the process with Go 1.13 by tentatively accepting the following proposals at the beginning of the current dev cycle (beginning of February 2019):
1. Go 2 number literal changes
This comprises an overhaul of the valid notations for number literals. Specifically, binary integer literals (e.g., 0b1010); an alternative, more modern notation for octal numbers (e.g., 0o677); support for hexadecimal floating-point numbers (e.g., 0x1.2p-3); and finally the ability to use the underscore (‘_’) character to separate digits for improved readability (e.g., 0x_1234_5678). These proposals are discussed at:
golang.org/issue/19308 (binary integer literals)
golang.org/issue/12711 (octal integer literals)
golang.org/issue/29008 (hexadecimal floating point)
golang.org/issue/28493 (digit separator)
2. Signed integer shift counts
This proposal permits the use of signed integers as shift counts and is expected to significantly reduce the need for (superficial) uint conversions. Discussion is at:
We have landed the necessary changes at tip in early February of this year. Per the blog post, we will make the final decision regarding the acceptance of these new language features shortly after the dev freeze, in early May.
(Our blog post also proposed adopting issue #20706 General Unicode identifiers based on Unicode TR31. This turned out to be more complicated than expected, and we dropped this proposal from the original list.)
This is a last call for feedback. Please submit any comments you may have on the respective issues in the issue tracker. Use the thumbs-up emoji to express general approval. Instead of a thumbs-down, please comment as to why you believe the respective feature should not be included.
Thanks for your feedback and all your help improving Go!
Robert Griesemer, for the Go Team
Is https://github.com/golang/go/issues/29934 also part of this process?
Threads like that sometimes generate useful discussion, or sometimes just end quickly, but it seems it could be worthwhile to reach out more broadly than golang-dev for a final round of feedback.