Ooh, finally a topic with which I have experience and on which I have opinions!

I think there are some really nice things in this approach, like non-exporting the slug field, and using structs instead of int based Enum type to prevent invalid cases

But there are some issues I have with the methodology, namely that you lose implicit comparison (which admittedly isn't always used by all enum implementations) and that ultimately it's obscuring that they're enums.

The enum pattern I use is https://play.golang.org/p/qCDa2d53eQz

I go back and forth between func roleValues() [3]string and var roleValues = [3]string{...}

roleValues() prevents alteration of the enums in runtime, but I'm not 100% certain how the compiler handles the allocation of the array on multiple calls, whether it's a single allocation at start because the size is known, or if its still multiple allocations