nits on BigInt Proposal

[Maggie Pint]

The Node team was one of the biggest supporters for this proposal as it
enabled much better interoperability with the host environment.

My temporal proposal is kicking around depending on bigint to allow
nanosecond precision timestamps, which are common in scientific
applications.

For myself as a general purpose web dev, I like the idea of no frills
integer math. Doing integer math with the number type is mildly annoying
sometimes.

On Aug 4, 2017 7:52 AM, "kai zhu" <kaizhu256 at gmail.com> wrote:

> looking at the use-cases for this feature @ 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?
>
>
>
> _______________________________________________
> es-discuss mailing list
> es-discuss at mozilla.org
> https://mail.mozilla.org/listinfo/es-discuss
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20170804/c248162e/attachment.html>