-
Notifications
You must be signed in to change notification settings - Fork 645
Find all references/implementations won't show where the method is called #3140
Comments
What is the output of |
@stamblerre Thank you for the reply.
|
And gopls logs:
|
@stamblerre I think this is the current limitation of |
Ah, thanks @hyangah, I should've read the repro before asking for extra data 😄 On golang/go#35999, @muirdm said:
Which was the reason that idea was abandoned. Maybe we could support this if there are no references results, or would that be too hacky? |
I reopened the upstream issue, so let's shift the conversation there, and I'll close this issue. |
Thanks guys. @stamblerre @hyangah |
What version of Go, VS Code & VS Code Go extension are you using?
go version
to get version of Gocode -v
orcode-insiders -v
to get version of VS Code or VS Code Insiders0ba0ca52957102ca3527cf479571617f0de6ed50
x64
go env GOOS GOARCH
to get the operating system and processor architecture detailsamd64
Share the Go related settings you have added/edited
"go.useLanguageServer": true
Describe the bug
Find all references/implementations won't show where the method is called when this method is defined in an interface and implemented somewhere.
A clear and concise description of what you expected to happen:
Find all references/implementations should show
p.print()
in line 16 in screenshot below.Steps to reproduce the behavior:
In the screen shot below, when right click on
print()
in line 19 and choose "Find all references/implementations", Vscode cannot see what's in line 16.This is the case that they are in the same file, it takes a lot more effort to figure out who called this method when they are in different files.
Thank you!
Code for test:
Screenshots or recordings
If applicable, add screenshots or recordings to help explain your problem.
The text was updated successfully, but these errors were encountered: