js BigInt

[timotheecour]

links

• js: use BigInt instead of Number for int64, int · Issue #187 · nim-lang/RFCs
• https://forum.nim-lang.org/t/6342#39140
• [WIP] new module jsarrays: ArrayBuffer, DataView + typed js API's by timotheecour · Pull Request #14128 · nim-lang/Nim
• 2 TITLE: performance comparison: node-int64 vs BigInt; un-deprecate node-int64? · Issue #21 · broofa/node-int64
• EDIT: BigInt64Array and BigUInt64Array, refs developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/BigInt64Array

safari support

• 179001 – [ESNext] Implement support for BigInt

polyfills/emulation

• peterolson/BigInteger.js: An arbitrary length integer library for Javascript
• GoogleChromeLabs/jsbi: JSBI is a pure-JavaScript implementation of the official ECMAScript BigInt proposal.

misc

• https://floating-point-gui.de/languages/javascript/

• Add js BigInts by juancarlospaco · Pull Request #16409 · nim-lang/Nim

• c++ => js via cheerp: A fast BigInt.js in an evening, compiling C++ to JavaScript | by Carlo Piovesan | leaningtech | Medium
  generated js: https://github.com/carlopi/BigInt.js/blob/master/BigInt.js
  https://medium.com/@timothee.cour/did-you-benchmark-this-when-targetting-wasm-instead-of-js-4f98443699b7?source=responses-----db61ae733512----0----------------------------

uint64, int64

https://v8.dev/blog/bigint

For example, if we see that relatively small BigInts (up to 64 bits) are an important use case, we could make those more memory-efficient by using a special representation for them:

[timotheecour]

• check whether we should remove the {.error.} procs from Add js BigInts nim-lang/Nim#16409; they break overloadExists from resolveSymbol(foo(args)) and overloadExists(foo(args)) to return symbol after overload resolution nim-lang/Nim#12076 (and also, maybe, declared; note that compiles is less efficient than declared and overloadExists)