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
x/tools/cmd/guru: add type position to 'describe' output #27308
Comments
CC @alandonovan |
Also cc @ianthehat |
Ping @alandonovan and @ianthehat. If you decide this is OK or decide what you want instead, it sounds like @hummerd has an implementation. |
Ping @alandonovan and @ianthehat. |
Yes, it seems like a reasonable feature. If you send me the CL I will review it. Thank you. BTW, longer term, the Go team at Google will maintain a canonical LSP (language server protocol) implementation, which will subsume most of the features of Guru. In hindsight some of its features such as pointer analysis-based callgraph alias queries do not carry their weight (performance, implementation complexity) and should be dropped or replaced by simpler approximations. I expect that the feature described in this issue is part of the core LSP feature set. |
I am not understand, I go google or Microsoft ?? |
Great news about LSP! |
Add typepos field to json output of describe command. This field shows where type of current (under cursor) identifier is defined. This will help code editors implement command 'Go to type definition'. Implements [#27308](golang/go#27308) Change-Id: I4e02ddbdc03fecec98135b8996f9562a88a9cfb8 GitHub-Last-Rev: be47e39 GitHub-Pull-Request: #50 Reviewed-on: https://go-review.googlesource.com/c/140379 Reviewed-by: Alan Donovan <adonovan@google.com>
It looks like this was implemented in CL 140379, closing. |
It would be nice to have command like 'Go to type definition' in code editors. To help implement this we need to know where type of current (under cursor) identifier is defined.
So proposal is to add "typepos" to json output of describe identifier.
P.S. I am ready to create PR just wanted to discuss this before
The text was updated successfully, but these errors were encountered: