New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cmd/go: module work & spam when running 'go doc' on a standard-library package #31505
Comments
Related: #29452 |
See also #28992. |
Where did you execute |
I'm guessing that this is another side-effect of loading the build list eagerly, but switching it to lazy loading will require quite a bit of refactoring. (I've been hoping to do that for 1.13, but with the freeze looming it's not looking very likely.) |
|
If you can't fix this before Go 1.13, I think we should special case the std packages in cmd/doc. Goimports does. Std is super common & should be fast.. In fact, we should do that regardless. |
@bradfitz: Define 'special case'. That is, what do you want the command to do? |
@robpike, if I run something like:
It should recognize that In goimports we have this auto-generated file that gives goimports that info for what is known to be in std (and thus in $GOROOT): https://github.com/golang/tools/blob/master/imports/zstdlib.go |
I can do that, but I can't help thinking there is something much deeper that needs fixing and papering it over is a mistake. |
Just a drive-by thought - does For example, what should |
I believe this has been fixed by changes to module support elsewhere. Please reopen if not. |
I'm trying to read about strconv and modules seems to be trying to do work?
/cc @bcmills @jayconrod
The text was updated successfully, but these errors were encountered: