From my point of view, no generics, error handling boilerplate, no real enums (although there is a kind of workaround).
There are other issues regarding tooling, specially for the use cases that I care, like dynamic loading into other platforms (JVM and .NET), GPU programming and graphical debuggers.
So naturally many C++ dev did not felt at home with Go.
https://commandcenter.blogspot.com/2012/06/less-is-exponenti...
Those pain points are the biggest roadmap points on a possible 2.0 version.
Would you mind expanding on this point? Where I work, we do lot of C++ for the reasons you described but I have started to learn Go to see if its a suitable replacement.