Float32.toText and Float32.format produce output that varies between moc versions and runtime configurations, making their doc examples non-assertable.
Currently both examples are marked no-validate for this reason:
Float32.toText(1.5) — the text representation may differ (e.g. "1.5" vs other formats)Float32.format(123.0, #exp 3) — the exponential format string may differ
This is analogous to Float.toText and Float.format which have the same no-validate treatment.
It would be worth stabilizing the output of these functions across moc versions, or at least documenting the exact guarantees. Tracked here so the no-validate annotations can eventually be removed.
Float32.toTextandFloat32.formatproduce output that varies betweenmocversions and runtime configurations, making their doc examples non-assertable.Currently both examples are marked
no-validatefor this reason:Float32.toText(1.5)— the text representation may differ (e.g."1.5"vs other formats)Float32.format(123.0, #exp 3)— the exponential format string may differThis is analogous to
Float.toTextandFloat.formatwhich have the sameno-validatetreatment.It would be worth stabilizing the output of these functions across
mocversions, or at least documenting the exact guarantees. Tracked here so theno-validateannotations can eventually be removed.