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
i made a design decision to always decode numbers in 'exponent' form to floats but this means you can't represent anything larger than ~1.78e308
do you actually see these values in use? i surveyed common json libraries and most made the same design decision i did, but if this is an actual real world problem i can look at adding support for integer 'exponent' decoding in v3.0
Many thanks for the explanation. This problem is not a real world problem. I have only generated test data based on the ECMA standard. I am quite happy if you want to close this issue (perhaps a note in the documentation ?).
If the sign after the e/E is '+' or missing, the number of the following digits seems to restricted to 3:
The text was updated successfully, but these errors were encountered: