DynaMix VS AnyAny

The thing is, that if something can be done with vanilla C++ polymorphism, virtual functions and inheritance, the DynaMix equivalent will look clunky and bloated. For example, you can see the exact same thing implemented with virtual functions and inheritance, with std::function and with DynaMix in the unicast benchmark

https://github.com/kelbon/AnyAny trait(add, void(int), self.add(args...));

i dont know what he means, but with this type erasure library you can have non virtual interface and still use dynamic polymorphism with those types, so you dont need choose *do i need to do this type polymorphic* etc

There are also invoking from tuple and curring (just an example of technique)https://github.com/kelbon/AnyAny/blob/main/examples/functional_paradigm.hpp

As for my example containers: https://github.com/kelbon/AnyAny/blob/main/include/data_parallel_vector.hpp

variant_swarm - container which behaves as set of std::variant, but with much faster visit operation and operation for getting view to all values of type T. It short, it just stores all types separatelly and supports operations visit, view, also you can change underlying containers for Ts..., it is std::vector by default https://github.com/kelbon/AnyAny/blob/main/include/variant_swarm.hpp

Its part of my library for working with polymorphic types.

Good idea selling Rust from behind enemy lines soldier! My god, your readme doesn't even mention Rust, wonderful!

https://github.com/kelbon/AnyAny here you can see how it implemented, for example