Magic Enum C++ VS Bitsery

I'm not sure this is quite what you're asking for, but this library has been super helpful to me in the past : https://github.com/Neargye/magic_enum

Also, a shoutout to Magic Enum: https://github.com/Neargye/magic_enum

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

I’d recommend checking out bitsery for some ideas, I’ve really enjoyed using it. https://github.com/fraillt/bitsery

Thanks for sharing https://github.com/fraillt/bitsery it seems more powerful but require quite a boilerplate code for even very simple composite stuff. With ByteStream you can totally forget about deep you are in the data-structure hierarchy.

Bitsery is the closest I've seen to it, but you have to use extensions (which i can't yet figure out the API for) to make it achieve byte for byte compatbility

But you could also look into something like bitsery which seems to make it easier to choose how you encode certain fields, without schemas existing outside your code. https://github.com/fraillt/bitsery

If size and performance matter, then take a look at bitsery. * it might be 9x+ faster than cereal and 18x faster than protobuf. * size-wise, you might save 20-30% by default * on top of that you additional might opt-in into: * bit-level serialization control (e.g. if your values are in the range 1000-2000 it will take you 10bits, or use VLE) * backward-forward compatibility support * pointer support, including raw pointers with the ability to provide custom allocator. * and powerful extensions system, which allows you to further customize things in any way you want it :)

About on par with nlohmann is a binary serialization lib called Bitsery. It's easy to use, and will be a lot more performant than json. The downside is that the serialized data won't be human readable.