Closed
Bug 757256
Opened 13 years ago
Closed 7 years ago
Provide Big Integer math support for JS
Categories
(Core :: JavaScript Engine, enhancement)
Tracking
()
RESOLVED
DUPLICATE
of bug 1366287
People
(Reporter: jrconlin, Unassigned)
References
()
Details
(Whiteboard: [js:t])
It would be swell to provide Big Integer support in javascript.
I'm doing some native client crypto work, but I can see where very large integer support would be awfully useful for things like graphic work, or scientific modelling. If nothing else, having local support for large integers would make Firefox a rather compelling choice.
(There. Filed. Itch scratched. Feel free to "WONTFIX" this once you're finished laughing or cringing.)
Comment 1•13 years ago
|
||
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Comment 2•13 years ago
|
||
Not a dup -- bignum != int64.
/be
Comment 3•13 years ago
|
||
Ah, sorry, I had assumed that you were doing the full object value strawman in that bug.
Comment 4•13 years ago
|
||
The strawman is expansive (or perhaps just vague :-P): "We add new types such as uint64, int64, and bignum (and probably smaller int types as well)."
But bug 749786 is specific: "prototype int64/uint64 value objects, with operators and literal syntax".
/be
Status: REOPENED → NEW
Updated•13 years ago
|
Whiteboard: [js:t]
Comment 5•12 years ago
|
||
Show me BigInteger and a way to implement value objects in JavaScript, and I'll show you BigDecimal implemented as a .js file. :)
Comment 6•12 years ago
|
||
I'll even throw in "digits on demand" for non-terminating decimals using yield.
Comment 7•11 years ago
|
||
There is a BigInteger type in WebCrypto (http://www.w3.org/TR/WebCryptoAPI/#big-integer) though I suppose a "proper" BigInteger implementation should go into / is in ES7. See Bug 865789 for the WebCrypto implementation.
Assignee | ||
Updated•10 years ago
|
Assignee: general → nobody
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago → 7 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•