Here’s how `uarray` solves each of these issues:

1. Backends… There is no default implementation.
2. This is handled by (thread-safe) context managers, which make switching easy.
3. There’s one coercion function per type of objec
• Libraries are only asked to dispatch over objects they know how to convert, so there’s no backwards-incompatible break when we add dtypes or ufuncs.
• Conversion can be as simple as lambda x: x.
• There’s a generic dispatcher and reverse dispatcher per function, with “marks” to indicate the type of object.
4. Arrays are just one “type” of object you can dispatch over, so there’s no repition by definition.