Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
cmd/go: make 'cmd/internal/load' public #25998
For a piece of build-related tooling, I recently had call to list the
I'd like to propose that at least a public-facing interface over
he consequence of the
I can appreciate that position, but in terms of building go tooling in go, the
Conversely, as I've dug in further, aspects of this tooling refer out e.g. to
My immediate use case here is "what packages are available to import", which turns out to be a knotty problem. (My personal chestnut has to do with multple entries in the GOPATH.) Does it make sense for that task to get reimplemented?
The go tool is being used in various scripts, so in effect we are locked in to its general behavior. The go/build package was an idea that I think has not worked out all that well as ideas have moved forward.
I believe that the question of "what packages are available be import" is answered by