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
{{ message }}
This repository has been archived by the owner on Sep 19, 2018. It is now read-only.
last week I stumbled upon an issue regarding the encoding/decoding of floating point values. As far as I can see I have to deal with all the accuracy problems of Doubles when it comes to floating point values in the current implementation.
Therefore I tried to implement the support of Decimal for encoding and decoding as contribution. Encoding went well, but when it comes to Decoding the solution is not that straightforward.
After looking into the JSONParser I understand that the parser itself is using Doubles when it comes to parsing floating point numbers.
Has anyone thought of a strategy to improve the handling of floating point numbers in Freddy yet?
Kind regards,
Alexander
The text was updated successfully, but these errors were encountered:
Unfortunately, after a few attempts on our end the decoding path isn't well-defined without breaking existing clients. Freddy is in maintenance mode and only seeking to make bug fixes at the moment. Please reopen if you have more thoughts on an implementation. Thanks for the suggestion.
Hi,
last week I stumbled upon an issue regarding the encoding/decoding of floating point values. As far as I can see I have to deal with all the accuracy problems of Doubles when it comes to floating point values in the current implementation.
Therefore I tried to implement the support of
Decimal
for encoding and decoding as contribution. Encoding went well, but when it comes to Decoding the solution is not that straightforward.After looking into the
JSONParser
I understand that the parser itself is using Doubles when it comes to parsing floating point numbers.Has anyone thought of a strategy to improve the handling of floating point numbers in Freddy yet?
Kind regards,
Alexander
The text was updated successfully, but these errors were encountered: