Closed
Bug 1631702
Opened 5 years ago
Closed 4 years ago
[meta] Ship BigInt <-> Int64 interconversion at JS/wasm boundary
Categories
(Core :: JavaScript: WebAssembly, task, P1)
Core
JavaScript: WebAssembly
Tracking
()
RESOLVED
FIXED
People
(Reporter: lth, Assigned: asumu)
References
Details
(Keywords: meta)
Metabug that is intended to block only those bigint <-> int64 interconversion work items that prevent us from letting this feature ride the trains (it has been live on Nightly for quite some time). Nice-to-have features that don't block shipping should block bug 1608770 instead.
The feature is not yet at Phase 4 in the Wasm CG, but nothing appears to prevent that from happening soon.
Proposal text: https://github.com/WebAssembly/JS-BigInt-integration
Phase 4 ticket: https://github.com/WebAssembly/JS-BigInt-integration/issues/32
|
Reporter | |
Updated•4 years ago
|
Severity: -- → N/A
Priority: P2 → P1
|
|
Reporter | |
Updated•4 years ago
|
Assignee: nobody → asumu
Status: NEW → ASSIGNED
|
||
Updated•4 years ago
|
Keywords: dev-doc-needed
|
|
Reporter | |
Comment 1•4 years ago
|
||
Currently in Beta 78 but we'll keep this bug open until the last blocker is closed too (test cases).
|
|
Reporter | |
Updated•4 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
|
|
||
Updated•4 years ago
|
Keywords: dev-doc-needed
You need to log in
before you can comment on or make changes to this bug.
Description
•