I just put it here.
Will take a closer look later today but what I’ve seen so far does not looks good. Pollution of global namespace with mixin’s methods, enforcement of components-only design ( as opposed to optional implementation of interfaces & possibility to include reusable components in my case). I also don’t like having access to mutation by everyone. And to hide it I would have to write wrapper over mixin class.
In my version I have everything I need with only overhead being array lookup by compile-time index. And virtual function call if component is an implementation of interface.
We should not use this library directly, however it is the only solid example of runtime mixins for c++ I`ve found.