A lot of the proposed value-add seems like the authors aren't aware the built-in `type()` can dynamically modify class definitions.
Getting rid of `hex(id(self))` in `__repr__` is regressive UX.
@typedispatch seems like both a slow way of using 'isinstance()' and a FOMO C++ virtual function bloat.
What's costlier, the new stack frames plus conditional for a decorator or the `elif isinstance()`s in one function definition?
How does a programmer reference the correct function definition by name if they're using @typedispatch instead of `isinstance()`?
I'd suggest you stop comparing typed dispatch to virtual functions in C++, because they have nothing in common. If you want to draw parallels, make sure to use a suitable analog.