I think sometimes it's important to accept the shortcomings of the language we're using instead of chasing high overhead abstractions like the one presented in

I think sometimes it's important to accept the shortcomings of the language we're using instead of chasing high overhead abstractions like the one presented in the OP and in the enumer package. I hate that go doesn't have enums, I hate that it doesn't have tagged structs, but if I spend my time trying to massage the language into simulacra of them, I'm losing time that I could spend writing productive code, or I muddle the waters for future developers that will have to deal with those abstractions in the future. Overall I think it's not worth it, outside of highly theoretical implementations like this, that can exist independent of code that actually does things.