Equinox-Engine VS Magic Enum C++

My little toy engine I made had code for this. I had to rely on gnu extensions, but it worked ok. Then I would define them in lua from the c++ code so I could use them easily. https://github.com/floomby/Equinox-Engine/blob/main/enum_helper.hpp

What does this have to offer over magic_enum?

But it's a hack, and I prefer not to use hacks in production, because of their significant limitations:

Why reinvent the wheel? magic_enum

I strongly recommend that you instead use magic_enum::enum_cast

Magic Enum provides that.

While I can understand the sentiment behind that it makes for a poor solution because people seeing the enum will assume it's a valid entry. A better solution is to use something like magic enum for that case.

magic_enum by far. It has an extreme amount of black magic, and compiler specific stuff all abstracted away behind its extremely neat user interface.

magic_enum

To my knowledge magic_enum has some severe limitations; for example, it limits the range of enum values, it cannot handle duplicate enum values, it uses compiler-specific hackes, etc. There is a list of all of them here. [1]

And I'm glad to see interest! I can definitely add string -> enum conversion—I'll see if I can do that right now in fact, it might not take long.

[1] https://github.com/Neargye/magic_enum/blob/master/doc/limita...

It also has really cruel limitations, defaulting to MAGIC_ENUM_RANGE_MAX = 128! It will quietly fail if you try to use this with Vulkan enums for example.