-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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/gopls: "inline: corrupted reference %v" bug in golang.RemoveUnusedParameter #69896
Comments
The failing assertion checks that each reference to the function or method of interest is a call to to a symbol with the same name and package as the original function. But the |
Thanks, that was indeed it, and I was able to reproduce. Fix incoming. |
Change https://go.dev/cl/628376 mentions this issue: |
Issue created by stacks.
This stack
u1wk7A
was reported by telemetry:gopls/bug
golang.org/x/tools/gopls/internal/util/bug.report:+35
golang.org/x/tools/gopls/internal/util/bug.Errorf:+2
golang.org/x/tools/gopls/internal/golang.inlineAllCalls:+98
golang.org/x/tools/gopls/internal/golang.rewriteCalls:+114
golang.org/x/tools/gopls/internal/golang.RemoveUnusedParameter:+81
golang.org/x/tools/gopls/internal/server.(*commandHandler).ChangeSignature.func1:+2
golang.org/x/tools/gopls/internal/server.(*commandHandler).run.func2:+3
golang.org/x/tools/gopls/internal/server.(*commandHandler).run:+73
golang.org/x/tools/gopls/internal/server.(*commandHandler).ChangeSignature:+2
golang.org/x/tools/gopls/internal/protocol/command.Dispatch:+39
golang.org/x/tools/gopls/internal/server.(*server).ResolveCodeAction:+21
golang.org/x/tools/gopls/internal/protocol.serverDispatch:+46
golang.org/x/tools/gopls/internal/lsprpc.(*streamServer).ServeStream.ServerHandler.func3:+5
golang.org/x/tools/gopls/internal/lsprpc.(*streamServer).ServeStream.handshaker.func4:+52
golang.org/x/tools/gopls/internal/protocol.Handlers.MustReplyHandler.func1:+2
golang.org/x/tools/gopls/internal/protocol.Handlers.AsyncHandler.func2.2:+3
Dups: vmzEcA
The text was updated successfully, but these errors were encountered: