Dear golang-nuts, As https://github.com/golang/go/issues/27151, https://github.com/golang/go/issues/6853 and many relevant issues discussed, Go download is huge.
The Go download contains everything in the main repo. Since Go modules are now a success, is it considered to separate all runtime irrelevant (meaning, no need runtime support to implement, e.g. net poller need runtime support because there is a scheduler) libraries out of the main repo? For instance, the following packages can be separated to be stored in a different repository, called std module: std/archive std/bufio std/bytes std/compress std/container std/context std/crypto std/database std/encoding std/errors std/expvar std/flag std/go std/hash std/html std/image std/index std/io std/log std/math std/mime std/path std/plugin std/regexp std/sort std/strconv std/strings std/syscall std/testdata std/testing std/text std/unicode Say we have a separate repository called golang/std, import these packages can have the same import path, instead of "std/io", go modules can overwrite the import path exactly like what it did for "github.com/user/mod/v2", set the imported std modules in go.mod file, import as "io" directly. Thanks for reading. Changkun -- 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/4a6b9418-a15d-4f71-8993-2b41f3fba068%40googlegroups.com.
