You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
jayconrod opened this issue
Oct 7, 2019
· 0 comments
Labels
GoCommandcmd/goNeedsFixThe path to resolution is known, but the work has not been done.ToolsThis label describes issues relating to any tools in the x/tools repository.
cmd/doc currently uses go/build.Import to locate and import packages. It should use golang.org/x/tools/go/packages.
This may be a little complicated because cmd/doc supports a number of shorthand formats for specifying the package to display documentation for, so we may not have the full package path. However, go/build has limited support for modules, and we're considering deprecating it eventually. Using go/packages could also simplify cmd/doc, since it wouldn't need code for parsing Go source.
The text was updated successfully, but these errors were encountered:
jayconrod
added
NeedsFix
The path to resolution is known, but the work has not been done.
GoCommand
cmd/go
Tools
This label describes issues relating to any tools in the x/tools repository.
labels
Oct 7, 2019
GoCommandcmd/goNeedsFixThe path to resolution is known, but the work has not been done.ToolsThis label describes issues relating to any tools in the x/tools repository.
cmd/doc currently uses
go/build.Import
to locate and import packages. It should usegolang.org/x/tools/go/packages
.This may be a little complicated because cmd/doc supports a number of shorthand formats for specifying the package to display documentation for, so we may not have the full package path. However,
go/build
has limited support for modules, and we're considering deprecating it eventually. Usinggo/packages
could also simplifycmd/doc
, since it wouldn't need code for parsing Go source.The text was updated successfully, but these errors were encountered: