go-enum VS goimports

While not perfect, there are ways to generate enums automatically using go:generate, e.g. https://github.com/abice/go-enum

I wouldn't write a macro to save a couple of lines, but I would definitely use (not even write, just use) a macro for something like generating enum [de]serialization for both JSON and BSON in one line. Go, even with generics, still has no way of abstracting extremely common patterns like enums without separate generator tools. Clearly someone thought the macro was useful here, but without a macro they had no choice but to write a separate tool.

Ive found enums in Go are a pain point, especially across an organization because there are many valid ways to implement it. It's also fairly verbose to implement. The way Ive solved for it is code generation. This is a pretty good library that my team uses in production https://github.com/abice/go-enum

I've worked in a few different languages and Go doesn't seem all that unique in the way that it doesn't provide an ENUM primitive. However, I looked around a bit and found go-enum which seems pretty neat. Also, I have no problem writing a custom string or int/iota type. In some cases you want to be able to serialize/deserialize with them -- and in others you don't need that.

Along that same line you can take it a step further and generate the iota block too with this tool https://github.com/abice/go-enum

Looks like this does what you want: https://github.com/abice/go-enum

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.