In current V8, NaN values carry their observable representations around with them — e.g. f64ArrA[0] = f64ArrB[0] preserves bits, doesn’t map to 0x7FF8000000000000. I thought this was something that stopped a long time ago, is this a regression or something I’m remembering wrong?
-
-
V8 doesn't canonicalize NaNs in general. We do for holey arrays because we represent to hole as a special NaN.
-
That said, I think that makes us spec-incompatible: https://tc39.es/ecma262/#sec-rawbytestonumeric …
- 6 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.