[+cc golang-nuts, it was lost at some point] I find it unexpected that to compute a version you need information not from one, but from two places that use very similar but ultimately different syntax.
In vgo the major version has to be specified in Go import paths, and the minor version needs to be specified in go.mod file, which is not Go code but looks very similar to Go code. Why not just use Go code throughout? We could extend Go syntax in a backwards-compatible way to be able to express all the information contained in the go.mod file. The bulk of the code would continue to import old-style, "bare", imports, while a single, or perhaps a small number of Go files would encode the information required for version management using new-style imports. Perhaps this file, or files could have standardized names, zmod.go, or whatever (please don't bikeshed the name). These files could be guarded by build-tags, so old compilers ignore them, just like how old compilers ignore the go.mod file. -- Aram Hăvărneanu -- 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. For more options, visit https://groups.google.com/d/optout.
