te VS AnyAny

Or dyno or Poly or Not-Actually-Boost.TE or ...

https://github.com/boost-ext/te Boost TE ("unnoficial boost project")

https://github.com/boost-ext/te (for SBO performance and type.erasure call syntax)

And if it were in the standard there wouldn't be at least five well known libraries implementing it (including from Adobe and from Facebook): https://github.com/boost-ext/te#similar-libraries

As far as I know (I don't really follow the committee work) the latest attempt to introduce run-time duck-typing in the standard was https://github.com/andyprowl/virtual-concepts, which seems dead.

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