Re:TOML: Tom's Obvious Minimal Language
by no_wizard on Sunday May 21, 2023 @03:48PM
(#36024145)
Annoyingly, it also doesn't support BigInt, which would alleviate this problem in JS as well
[ Parent
| on HN ]
A number in JSON can have an arbitrary number of digits, i.e. it can represent any BigInt value.
Re:TOML: Tom's Obvious Minimal Language
by Supermancho on Sunday May 21, 2023 @06:08PM
(#36025101)
> A number in JSON can have an arbitrary number of digits, i.e. it can represent any BigInt value.
In my experience, violating type constraints causes problems in downstream systems (usually with parsing or trying to operate on invalid values).
Number, as defined by the JSON Schema spec. A 32-bit signed integer. It has a minimum value of -2,147,483,648 and a maximum value of 2,147,483,647
BigInt is defined by various (MSFT, MySQL, etc): -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807
Most systems use a JSON String for large numbers, out of necessity, not JSON Number.
In context, BigInt refers to arbitrary precision integers [1], rather than any particular size of integer, hence "arbitrary number of digits".