Ichor VS kangaru

More information on the async I/O can be found in the docs.

Ichor v0.2.0 has been released today: https://github.com/volt-software/Ichor/releases/tag/v0.2.0

supporting `co_await` for handling events as well as providing an example HTTP implementation showcasing `co_await`.

I've been working on and off as time permits on Ichor. It's a c++ middleware designed to take away a couple problems I had with writing large scale applications:

Kind of tooting my own horn here, but I agree with you and have therefore written my own DI-esque library, Ichor. It does support the use-case of resolve-per-graph, but does this through what Ichor calls filters. Essentially, every created dependency can have a custom filter installed that allows run-time control of which requesting entities are requesting it. The repository has some code examples for you to look at. I'm pretty (but not completely) happy with it.

I've been working on bringing C++20 to the soft-realtime domain through Ichor. I've already managed to get dynamic memory allocations to 0 by using memory allocators everywhere.

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.