That can be dealt with an output format. Just as the hex or octal or the "e" input format is lost.
With respect to the "e" notation Go seems to be an exception. Perhaps the sole one? Other prog languages I have used treat <int>e<int>as a floating pt. even in Go there is a slight inconsistency: 1e6 is an int but 1e-6 is a float. I find 1_000_000 clearer than 1e6. Not a big deal either way. > On Jun 22, 2016, at 8:17 AM, Michael Jones <michael.jo...@gmail.com> wrote: > > Sorry, I sent that too soon. > > One argument against underscores in numbers and other discardable syntax is > the tooling in Go to parse and regenerate go code, as in gofmt. It may be > more complicated to keep the “original input format” around and that is a > pretty good argument—unless that is already there for input values in hex. > > Michael Jones > michael.jo...@gmail.com > >>> On Jun 22, 2016, at 8:14 AM, Michael Jones <michael.jo...@gmail.com> wrote: >>> >>> https://github.com/golang/go/issues/42 >> >> Michael Jones >> michael.jo...@gmail.com >> >>> On Jun 22, 2016, at 7:29 AM, Roger Pack <rogerpack2...@gmail.com> wrote: >>> >>> Could you drop me a link to the discussion by chance? Seems this >>> feature is actually a reasonably common request :) > > -- > You received this message because you are subscribed to the Google Groups > "golang-nuts" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to golang-nuts+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
