Discussion

Background on why unxt works the way it does. These pages are for reading away from the keyboard — they discuss trade-offs and alternatives rather than giving instructions.

If you want to get something done, see the How-to guides; if you want to look something up, see the Reference.

• The sharp bits — the behaviours that surprise people, and why each one is inherent rather than a bug.

• Why Quantity is not parametric — why the default Quantity stopped encoding dimension in its type, and why the usual jit-cache explanation is wrong.

• Equality and equivalence — why == and unxt.equivalent answer different questions, and what that has to do with jax.jit.

• About unxt’s API conventions — why every operation has both a functional and an object-oriented form, and why the operator argument comes first.