Better Enums VS Experimental Boost.DI

I really like better_enums instead of magic_enums. There’s no limit on enum size with it: http://aantron.github.io/better-enums/

It was heavily used at a former employer of mine, so definitely a solid production-ready solution.

IIRC I then switched to another library doing the same stuff: https://github.com/aantron/better-enums It is not as magical, as it uses a special macro to define the enum, using dedicated syntax. So it only works for enums you yourself define. However, it did work a lot better for me with enums with huge values.

I can't keep up! First we have better enum, then some guy at a conference says we have to use wise enum instead, and now you speak of magic enum!

If you need a laugh today, look at Better Enums library for C++. If you thought moving from C to C++ would let you leave macros behind, think again! Enums in C++ still suck (a bit less than in C though), so someone built a library to help with that. And it's built on macros. So you can only have 64 entries per enum. And the library's code is barely readable.

I love: https://github.com/boost-ext/di for dependency injection

https://github.com/boost-ext/di (To detect constructor parameters and inject dependencies without runtime dispatch)

I was looking to try boost.di for some time, looks nice. https://boost-ext.github.io/di/

Things like Dependency Injection/Inversion are a little more cumbersome in C++ but certainly can be done, and I believe there's libraries for that as well (found a couple searching around, like fruit and boost-ext di ).

Dependency injection does not have to be dynamic, it can totally be done at compile time. Boost DI is an example: https://boost-ext.github.io/di/

Funny you mention dependency injection, proposed Boost.DI shall be up for Boost peer review probably in March. https://boost-ext.github.io/di/