3 ms·
But the point is to support large numbers with the traditional syntax. e.g. so that {"foo": 1234567890123456789012345678901234567890} doesn't lose precision.
by daurnimator 8y ago
But the point is to support large numbers with the traditional syntax.
e.g. so that {"foo": 1234567890123456789012345678901234567890} doesn't lose precision.
- elmigranto 8y agoGiven that `int + bigint` throws in JS, this exact thing will never happen imo, otherwise, you can't differentiate between types. Maybe something like `{"x": 10n}`, but at that point, might as well do reviver, especially if you already agreed on a format and use some to parse out class instances vs plain objects.