ENenneff·Aug 1, 2020
I agree that it would have been better to design these a little differently.
In the first case the go-import meta tag is totally unnecessary. The go tool and module proxy can discover git repos from an import path just fine. It’s only required for “custom” import paths where the path is some domain but the code lives somewhere else, like github.
In the latter case the decision to use go-source was actually made by the original author of godoc.org, not a google employee, and was done in coordination with another non-google initiative (gopkg.in) to make their source links work. So nothing to do with the go team really, sorry.
https://github.com/golang/gddo/commit/864b1c0aba009e37d30136...
If pkg.go.dev isn’t respecting go-source meta tags then that should probably be fixed. It would also imo be worth considering devising a more general, wel
Read the rest
l-known mechanism for doing this. Worth proposing I think!