> If we just put 'go dep' as the hook to current draft dep, then users would need to run things like 'go dep ensure' and so on, and those would be the first ever go sub-sub-commands. That feels not quite right to me.
From the commit message:
> We've avoided subcommands in the go command to date, and we should continue to avoid adding them unless it really makes the experience significantly better. In this case, it does.
So, I don’t see it as a contradiction to the mail you’re quoting :)
https://github.com/golang/go/commit/7aa9855704a766a1a16fbed7...
(main module does not need package generics)
I opened the original issue in question due to lack of feature parity and it got quickly closed (https://github.com/golang/go/issues/26610#event-1753880630). Then after some twitter back-and-forth (https://twitter.com/sgnn7/status/1022547467466956802) the issue got reopened.