I think one way to mark your code as implementing an interface is by doing the following:

import "fmt"

var _ fmt.GoStringer = (*S)(nil)

// S is a custom type.
type S struct {}

// GoString implements `fmt.GoStringer`.
func (s *S) GoString() string { return "" }

You can then use the find usages of your IDE to lookup usage of a that interface in your source, say that you have the following method, you'd be able to lookup the usage of fmt.GoStringer:

func Stringy(gs fmt.GoStringer) {
  // ... code goes here ...
}

You could also make such interface assertion statements just part of your test code that way it does not get compiled for the "release" version of your project.

• Source: https://dave.cheney.net/2017/06/11/go-without-package-scoped-variables

That's already a huge help thanks, still in addition a go vet type interface overview wouldn't hurt :P

I've never used it, but this was mentioned in an issue (#33270) the other day: https://golang.org/lib/godoc/analysis/help.html. It looks like it's exactly what you're looking for.

Your right the implements relation is exactly what I am looking for but maybe if that could be introduced in go doc also so you can do does analysis on just the package you are working on that would be perfect .

This sort of deep analysis is not really suited to cmd/go. It's a much better fit for the gopls tool.

Duplicate of #32973