Except that this write up says this was a deliberate design decision to trade space for speed. That's not something to be fixed, unless you convince Go to make different trade offs or to provide more optimization options.

In fact, there's a new issue opened (again, from Rob Pike) in response to this article: https://github.com/golang/go/issues/36313