TC39 Decimal_Measure
2025-07-16
plaintext logs
prev next
source on github
18:00
<sffc>

eemeli: For the Mixed Units proposal, Ben's README has examples like

    let footAndInch = new Measurement(5.5, {unit: "foot-and-inch"})
    footAndInch.toComponents()
    // [ {value: 5, unit: "foot"}, {value: 6, unit: "inch"}]
    footAndInch.toString()
    // "5 feet and 6 inches"

This requires unit conversion. Did you have in mind a way to implement mixed unit formatting without that?

18:00
<sffc>
Note: We already support ListFormat with type="unit", and you can glue together your own mixed unit format string if you have the individual values.
18:26
<eemeli>

One possibility, based on DurationFormat:

let nf = new Intl.NumberFormat('en', { style: 'unit', unit: 'foot-and-inch' })
nf.format({ foot: 5, inch: 6 })
20:21
<sffc>
I don't know if I want to open the can of worms of Intl.NumberFormat.prototype.format accepting a bag of fields
20:21
<sffc>
How do you feel about saying that mixed units will be shifted into the Smart Units proposal instead of their own proposal?
20:54
<eemeli>
I don't really see how they're connected, except as both advancing unit formatting? If that's enough, then maybe it makes sense to roll them up into one.
21:58
<sffc>
I mean, I'm not personally convinced that mixed unit formatting carries its own weight without the conversion half of the feature, since you can already get it manually by using a ListFormat to glue pieces together.
22:13
<eemeli>
That's fair. I'm not too invested in mixed units myself, so have no strong opinions here.