Home / Docs / Diagnostics
U2030: A unit conversion without an expected unit, or not exact
Release v0.4.0
A unit conversion has no expected unit, or is not exact.
Why Una rejects it
measured() and convert() take the unit they produce from the type their context expects (ADR 0104). measured() takes a unitless value, and convert() a measured one.
convert() moves between units of one dimension only by a positive integer ratio that fits the magnitude's integer type: from Kilometer to Meter it multiplies by 1000. The way down is written out, (d.magnitude() / 1000).measured(), so that the truncation of the division shows.
- On an
F64the ratio may be k or 1/k with k at most 2^53, and in edition0.5(preview) on anF32at most 2^24. - In edition
0.5(preview), on a decimal only k, since 1/k would round. - In edition
0.5(preview), a complex or a dense value does not convert as a whole.
The repair at a glance
src/demo.una
module demo
pub measure Meter
pub measure Kilometer = 1000 * Meter
- pub coarse(d: Int of Meter) -> Int of Kilometer = d.convert()
+ pub coarse(d: Int of Meter) -> Int of Kilometer = (d.magnitude() / 1000).measured()Failing example
una.toml
[package]
name = "demo"
version = "0.1.0"
edition = "0.3"src/demo.una
module demo
pub measure Meter
pub measure Kilometer = 1000 * Meter
pub coarse(d: Int of Meter) -> Int of Kilometer = d.convert()Fixed example
una.toml
[package]
name = "demo"
version = "0.1.0"
edition = "0.3"src/demo.una
module demo
pub measure Meter
pub measure Kilometer = 1000 * Meter
pub coarse(d: Int of Meter) -> Int of Kilometer = (d.magnitude() / 1000).measured()