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
tl;dr: we established that keeping a public field n: f64 that is derived from what essentially are fixed point data represented with integers is a source of potential precision loss, which isn't justified, given that the field isn't used.
While we could do more to make the API even nicer, an easy change we can do right away is to change n to be a getter.
This is a backwards incompatible change, which we should be OK with as all potential uses are in the icu4x repository.
The text was updated successfully, but these errors were encountered:
The field `n` is not used for plural selection, and may cause
precision loss in cases of conversion. So we stop keeping in
around and compute it on demand instead.
Fixesunicode-org#283
* Makes `PluralOperands::n` into a getter
The field `n` is not used for plural selection, and may cause
precision loss in cases of conversion. So we stop keeping in
around and compute it on demand instead.
Fixes#283
* fixup: simplify eval logic, clean up lint
This is based on the Slack conversation.
tl;dr: we established that keeping a public field
n: f64
that is derived from what essentially are fixed point data represented with integers is a source of potential precision loss, which isn't justified, given that the field isn't used.While we could do more to make the API even nicer, an easy change we can do right away is to change
n
to be a getter.This is a backwards incompatible change, which we should be OK with as all potential uses are in the
icu4x
repository.The text was updated successfully, but these errors were encountered: