go-enum VS goverter

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

Cool! Have you seen https://github.com/jmattheis/goverter ? I'm curious as to the pros and cons between the two.

Not directly, but you can define a custom implementation for the whole struct, see f.ex. https://github.com/jmattheis/goverter/blob/main/example/errors/input.go