You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@zbraniecki and @littledan have pushed back on the idea of performing math on units as part of ECMA-402's black box. For example, this proposal necesitates the ability to provide input such as "2 meters" and have that converted to the correct unit or units, such as "600 cm" or "6 ft, 3 in".
I can see both perspectives here. On the one hand, a third-party math library would be better suited to performing this arithmetic. On the other, the current proposal covers the full-stack i18n use case, and exposing the individual pieces would amount to a much larger API surface that we would need to design.
The text was updated successfully, but these errors were encountered:
Obviously not proposing this exact api, but is this the sort of abstraction level that is being suggested? This math seems like the exact sort of thing intl should be responsible for.
@zbraniecki and @littledan have pushed back on the idea of performing math on units as part of ECMA-402's black box. For example, this proposal necesitates the ability to provide input such as "2 meters" and have that converted to the correct unit or units, such as "600 cm" or "6 ft, 3 in".
I can see both perspectives here. On the one hand, a third-party math library would be better suited to performing this arithmetic. On the other, the current proposal covers the full-stack i18n use case, and exposing the individual pieces would amount to a much larger API surface that we would need to design.
The text was updated successfully, but these errors were encountered: