Magic Enum C++ VS outcome

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:

You can either write a to string(view) function for your enum or use https://github.com/Neargye/magic_enum

Why reinvent the wheel? magic_enum

Also if you want to convert enum members to string representation I suggest you just use magic_enum instead, much smaller dependency.

Magic Enum provides that.

https://github.com/ned14/outcome/tree/develop/abi-compliance uses both in a CI pass to ensure Outcome never changes anything which breaks either API or ABI with earlier versions.

outcome and/or expected

A "Sample Usage" appears on the front page of the docs: https://ned14.github.io/outcome/

I recently came across boost outcome as I was searching for a better error handling method. It took me a minute to get a hang of it but now I love it. After creating my own policy and a few aliases for easier use.

std::optional and std::variant can be a bit awkward to use in this scenario, though. Consider a dedicated type like boost::outcome (standalone versions) or one of the implementations of the proposed std::expected.

Minimum possible compile time impact is a key goal of https://github.com/ned14/outcome. We ship a single header edition which only includes the low impact standard headers as listed at https://github.com/ned14/stl-header-heft. We also don't use union storage for non-TC non-MB types in order to avoid complex metaprogramming execution by the compiler per instantiation.

It's really weird that I wrote the above, and then this bug was reported to Outcome: https://github.com/ned14/outcome/issues/244. Here is my exact complaint about lack of lifetime tracking in C++.