stillwater-sc / universal / 35320181350

86%

master: 84%

Build Type

push

github

Committed by web-flow

Commit Message

fix: five small manipulator and stream-extraction defects (#1551)

Batched because each is a handful of lines in its own header and splitting
them would cost five CI rounds. Each changes observable behaviour, and each
arrived with a decision its issue deliberately left open.

e8m0's to_binary ignored its nibbleMarker: the parameter was unnamed and the
separator unconditional, so mxfloat and nvblock could not turn the marker on
or off. e8m0 is eight exponent bits with no field boundary at all, so the '.'
it printed was a nibble marker wearing the field separator's character. It now
follows the tree convention: nothing by default, ' when asked (#1434).

hfloat's to_hex decoded the stored exponent unconditionally, so mathematically
equal zeros rendered differently -- 0x0.000000 * 16^-64 and * 16^-63 both came
out of a sweep of the hfp32 encodings. The test is on the fraction, not on
iszero(), which is stricter than its own comment claims and would have
normalised the canonical zero alone (#1448).

operator>> for lns and takum extracted into an uninitialised double and used
it unconditionally; on an already-failed stream the sentry fails, num_get
never runs, and the value is never written. A failed extraction now leaves the
target alone, matching native extraction and the rest of the tree, and dbns
joins them (#1450).

type_field(bfloat16) read a BfloatType::fbits that did not exist, and
components(areal) declared blockbinary<v.fbits> and called a decode() overload
that does not exist. Neither had ever compiled, because nothing instantiated
them. bfloat16 now declares fbits as every other float-like type does, areal's
components is rewritten against the real decode() signature, and both types
get a suite that instantiates their whole manipulator surface (#1453).

efloat's parse() began with clear(), which leaves the Normal state with no
limbs -- a value no arithmetic produces, not zero to iszero() or operator==,
printing as 0.000000e-01. Each failure path... (continued)

Coverage Stats

28 of 30 new or added lines in 8 files covered. (93.33%)

6 existing lines in 4 files now uncovered.

44762 of 52158 relevant lines covered (85.82%)

8784834.33 hits per line