> > but the others are needed for "go build" & co. > This can be solved by first issuing an std module first, then using go modules to import these packages for go build.
The idea is to separate compiler and runtime, then have a minimum go core distribution. The Go development process then can speed up and separate from std and core language. Just like tools in golang/tools repo. Moreover, right now, the issue tracker is now centralized in golang/go repo, which is verbose for the repo subscriber, a separate repo can also making a decentralized issue tracer possible. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/6fde727b-8075-47ca-8c05-d287d5380b04%40googlegroups.com.
