Go packages are statically linked into Go executables, yes. That doesn't mean that C libraries are, though -- and I think it's that level of static linkage that the parent meant.
If you're on macOS, try running $ otool -L some-go-program, or on linux:
If you're on macOS, try running $ otool -L some-go-program, or on linux: