-
Notifications
You must be signed in to change notification settings - Fork 645
Include the standard library in 'Go to Symbol in Workspace...' searching #1567
Comments
We would definitely not be overloading the existing Can you elaborate on your scenario here? Do you search for a symbol that you know for sure is part of the std lib? When doing so, do you also know which package it belongs to? If so, then have you tried the |
Also, if you are looking at searching for all symbols in given package, #671 is tracking that feature request |
The desired result is having the same functionality (namely a type-ahead search) that The main use case is for those times when I'm fairly sure of the naming of a symbol, but less certain of it's package location. The current solution is to either start typing in code and hope code sense picks up what I'm after, or heading to google. Neither of which are as effective as the behavior |
Would you know the package name at this point? |
|
Doesnt this scenario also extend to when using symbols from non std lib? |
It does, but with projects utilizing |
Ok, in that case we can have setting which when enabled can include the results from the std lib when the PRs are welcome. |
…1604) * When gotoSymbol.includeGoroot is set, also show symbols from GOROOT Setting the option to true enables the user to include the standard library located at GOROOT to be included in the results shown on "Go To Symbol" - resolves #1567 * Add proper types to empty arrays * Correctly lookup GOROOT by calling `go env` * tests * Move logic for retrieving symbols from goroot a level down
Thanks to @m90, this feature is now available in the latest update to the Go extension (0.6.79) |
It would be nice if symbols from the stdlib were included when using 'Go to Symbol in Workspace...'.
It appears that
go-symbols
only accepts one root and making multiple invocations might bet messy, so an alternative approach of having a 'Go to Symbol in Standard Library...' could be sufficientThe text was updated successfully, but these errors were encountered: