Non-finite results

NaN, the infinities, and signed zero. These are in the corpus for the cross-target comparison rather than for the reader. NaN is the one value WebAssembly does not fully pin: the payload bits, and the sign of a NaN produced from non-NaN operands, are both left to the implementation. So a NaN computed here and a NaN computed in a browser may differ in bits while being equally correct, and if those bits ever reached a snapshot the golden suite would fail for a reason that is not a bug. Every route to a NaN the language offers is therefore exercised, so that the native and WebAssembly snapshots have to agree on all of them. Undefined quotients and products.

{zero}_{over_zero}

\frac{0}{0}

NaN

{zero}_{times_infinity}

0 \cdot \infty

NaN

Out of domain. Nomo has no complex numbers, so these are NaN and not errors.

{root}_{of_negative}

\sqrt{0 - 1}

NaN

\log_{of_negative}

\ln (0 - 1)

NaN

{arcsine}_{out_of_range}

asin (2)

NaN

The indeterminate difference.

{infinity}_{less_infinity}

\infty - \infty

NaN

The infinities themselves are exactly representable and carry units.

positive

\frac{1}{0}

∞

negative

0 - \frac{1}{0}

-∞

{with}_{units}

\frac{1 m}{0}

∞ m

Signed zero is a real IEEE 754 distinction and a deterministic one, unlike a NaN payload, so it is pinned rather than normalised away. Note that 0 - 0.0 is positive zero: only unary negation reaches the other one.

{negative}_{zero}

- 0

{positive}_{zero}

0 - 0

0

{sum}_{of_zeros}

0 + {negative}_{zero}

0 + 0

0

The difference is observable, which is why it is worth pinning.

{reciprocal}_{of_negative_zero}

\frac{1}{{negative}_{zero}}

\frac{1}{0}

-∞