GoCover.io VS goimports

That was one of the options I considered. To create something reusable by others, though, I think that requires creating the Gist, configuring the Gist's URL and creating/configuring an authentication token. This OTOH just requires enabling the Wiki.

https://gocover.io/ https://github.com/vieux/gocover.io

Just a guess, but it might be somewhere in gopls https://github.com/golang/tools/tree/master/gopls/doc On this page https://langserver.org/ it says it should support "finding references"

Language server protocol. Here’s a good one: https://github.com/golang/tools/blob/master/gopls/README.md

gopls was not able to find modules in your workspace.When outside of GOPATH, gopls needs to know which modules you are working on.You can fix this by opening your workspace to a folder inside a Go module, orby using a go.work file to specify multiple modules.See the documentation for more information on setting up your workspace:https://github.com/golang/tools/blob/master/gopls/doc/workspace.md.

For more gopls settings, you can see files in this folder: https://github.com/golang/tools/tree/master/gopls/doc

But finding which interface is satisfied by a type is trivial anyways through gopls which integrates conveniently into any LSP supporting IDE (such as VSCode and Goland).

You need to make sure you have Google's lsp server for golang installed.