Sure, but in context Go doesn't have that issue. Go's compiler only supports Go in a more or less statically linked binary.
Go doesn't have this issue because there aren't other languages running on that runtime. If there were (and you wanted an interop of those languages with Go so that you could use Go libraries), then you'd have this issue regardless of the fact that the runtime is linked with the image.
Except for the fact that all CLR languages must adopt the same variance model, enforced by the runtime (or choose not to interoperate well).