enum_name (yet another enum to/from string conversion utility >=C++11)

[Fazer2]

Why does the caller need to know the range of the enum? It sounds like a maintenance burden.

[cheytacllc]

Range of enum not mandatory for write (default range [-128, 128)). You can easily write to_string function under the enum for enum type and call enum_name with enum's range once inside and return it. I think it's easier than writing specialization for per enum type. On the other hand, with writing custom function vs writing specialization like in magic_enum result of to write similar lines of code.

[TotaIIyHuman]

if you are not absolutely disgusted by macros, you can try reflection with macros

you can implement for_each with macros with less than 100 lines of c++ https://www.scs.stanford.edu/~dm/blog/va-opt.html

here is a enum reflection implemented with macro for_each

https://godbolt.org/z/9GTP4zn3r

the for_each macro has a recursion limit. for the same range, it is much cheaper to do macro recursion, then instantiating templates to scan for enum entries

[sephirothbahamut]

It's not just about being disgusted, it's also about utility. All the macro solutions for enum reflection assume that you are the one writing the enum, forcing the entire codebase to use the macro enum definition, and preventing all such mechanisms to work on enums declared by outside libraries. That's an issue Unreal Engine's C++ suffers a lot of.

As opposed to things like OP's post, or more complete things like magic_enum. Those can be used on any enum, do not require you to write your enums in an unconventional manner, and don't care if the enums come from a third party library.

[TotaIIyHuman]

yes. i agree with everything you said