1. 27
  1.  

  2. 1

    I worry about the weight/inertia of a change process where adding _ support within constant integers takes months of feedback and review (e.g. const MB = 1_024 * 1_024). At first glance, that seems like a straightforward and purely additive change so why the baggage?

    1. 4

      Because of Golang’s backwards compatibility promise it is crucial to ensure even “straightforward” changes are carefully considered. Once _ support is landed, it will not go away.

      1. 2

        Go isn’t somebody’s weekend hobby sandbox. Hundreds of thousands of programmers write code in it, lots of tools generate code for it, millions of lives and livelihoods are affected by code written in it. There is no “at first glance” on that level. Welcome to the big leagues.