misc/wasm: use {get/set}BigUint64 functions when BigInt hits stage4 #32785
Labels
arch-wasm
WebAssembly issues
FrozenDueToAge
NeedsFix
The path to resolution is known, but the work has not been done.
Performance
Milestone
{get/set}BigUint64 does not have full support yet
This is a reminder issue to change the code to the following once BigInt reaches stage4.
Coercion to and from BigInt and Number should be okay since we are anyways dealing with 2^53 bit integers.
Benchmarks do not show any noticeable difference mainly because the variance is so large:
name old time/op new time/op delta
DOM 101µs ±32% 98µs ±37% ~ (p=0.853 n=10+10)
But I guess this should be an improvement.
Related #32591
The text was updated successfully, but these errors were encountered: