so5-dining-philosophers VS RxCpp

I want to note that SObjectizer provides not only agents and dispatchers for them, there is also such a thing as message chains. They were introduced specially for the integration of non-SObjectizer-parts of an application with SObjectizer-part. But since then they grew to a full-fledged mechanism of building multithreading applications even without agents. You can take a look at our dining-philosophers demo (the description, the repository).

And, prior to that https://github.com/ReactiveX/RxCpp

Yeah, I know this problem with operators =), original RxCpp implementation also has this problem with implementing all functions into base class and calling dependent functions internally.

Also you can check rxcpp with documentation about reactive approach there. It is functional version of observer/publisher-subscriber patterns with ability to be multithreaded. You can send events from one side, subscribe from another and modify events in meanwhile

I use a very large header-only library RxCpp. Simply adding #include "RxCpp/rx.hpp" to one .cpp file adds >1 second of compilation time. I'd like to use it as a module, but when I try to import "RxCpp/rx.hpp";, I get a bunch of errors.

+1 for Rx, specifically RxCpp. I've used it in concert with Qt with great results.