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
As a result, the current conversion pipeline looks like u64 -> u32 -> f64. If it were u64 -> f64 (without u32), then we would not lose a significant range of numerical values (u32, f64].
I would be happy to review a PR that makes this change, otherwise I can add it to my list but I am not sure when I will have time to get to it.
FWIW the protobuf JSON representation recommends serializing 64-bt integers as strings, as f64 only has 52-bit precision, but I presume you are aware of this.
When I try deserialize next value, I've got an error "out of range integral type conversion attempted".
This happens because next function throw an error:
If look visit_u32 function, so number value wrapped in Kind::NumberValue which accept f64 type:
As a result, the current conversion pipeline looks like u64 -> u32 -> f64. If it were u64 -> f64 (without u32), then we would not lose a significant range of numerical values (u32, f64].
For example like this:
The text was updated successfully, but these errors were encountered: