nits on BigInt Proposal
kaizhu256 at gmail.com
Fri Aug 4 14:52:28 UTC 2017
looking at the use-cases for this feature @ https://github.com/tc39/proposal-bigint#use-cases <https://github.com/tc39/proposal-bigint#use-cases>, i'm not convinced it improves everyday programming, or outweigh the benefit and simplicity having a single number type.
my nits are:
- will this break or complicate existing/future code that does typeof checks for numbers? what are the costs of retooling nodejs mongodb / mysql / etc drivers and the apps that use them?
- how will JSON.parse and JSON.stringify deal with BigInt? the mentioned use-cases for wire-protocols, guids, timestamps, and fixed-point BigDecimal aren’t very useful if it can’t easily be serialized / deserialized across db / persistent storage
- are there actual common algorithmic use-cases in frontend programming or nodejs apps that need arithmetic on integers greater than 52-bits? should that rather be the domain of webassembly?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the es-discuss