* Brian Goetz: > But then we discovered that JSON5 also sneaks in some semantics, by > also supporting the exotic numeric values (NaN, infinities, signed > zero), which now has consequences for "what is a number", the numeric > representation, the API for unpacking numeric values, etc. (Having > multiple parsers is one thing; having multiple parsers that produce > different semantics is entirely another.)
But that's independent of JSON5: some data sources expected their numbers to be parsed as integers that require more than 53 bits to represent. That means double as the universal numerical type is out. BigDecimal would work, but may result in unexpected overhead. Thanks, Florian
