kangaru VS Experimental Boost.DI

This Fruit library is still on my TO-DO to review and try, but there is one other library that I wanted to try first, and it's called Kangaru. Both are DI injectors, but I can't say much more about them yet.

For example, in my game engine, the service configuration is in separated headers, and only the places that I'm using the library directly need those headers. See the page 13. Structuring Projects, this is where I'm talking about it.

Not lately, but I plan to get back into it. I'm making kangaru, a dependency injection container for C++ that reflects on constructor parameters to wire the classes together.

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/