dyno

Allows third-party and standard library types like std::vector to fulfill interfaces without modification, using parametric concept maps as shown in the README.

Polymorphic objects can be passed, copied, and stored naturally, eliminating the need for pointers or clone methods, and integrating seamlessly with C++ value-based APIs.

Provides policies like sbo_storage for small buffer optimization, enabling allocation-free polymorphism for objects under a configurable size, as demonstrated in the storage customization examples.

Vtable policies allow inlining hot functions or splitting vtables, reducing indirection and potentially outperforming traditional virtual calls, with selectors for fine-grained control.