On Tuesday, March 5, 2024 at 9:29:58 AM UTC-6 Bryan C. Mills wrote: The simplest way to download Go dependencies for code review and debugging is to run `go mod vendor` in your module or (newly added) `go work vendor` in your workspace. Also note that `go mod download -json` and `go list -m -json` now include origin information in most cases:
~$ go list -json -m go.uber.org/z...@v1.27.0 <http://go.uber.org/zap@v1.27.0> ... "VCS": "git", "URL": "https://github.com/uber-go/zap";, In switching to this, I had to pull the Module struct from src/cmd/go/internal/list/list.go and Origin from src/cmd/go/internal/modfetch/codehost/codehost.go While doing that and looking at the code, there are lots of interesting and good things in internal/ that can't be used. While I think I understand the reasons for internal/, I wonder if the GO compiler might be more immune to those normal reasons. In general: it's sage advice to never make the compiler people unhappy. Usually then lots of strange things start not working! In that regard, s/internal/workshop/ would denote things not yet stable. The compiler really only needing an example to demonstrate the usage package notinternal import { internal/notthis ) func CanCallThis() { notthis.ButNotThis() } That's my 2 cents there. It's fun to work with such an advanced language. -- 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/cb459c42-5be3-4280-b48d-8694499c3d88n%40googlegroups.com.
