Tzvetan Mikov
Tzvetan Mikov
Since this appears to be thread related, and happens even with single-threaded GC, I think we should at least carefully consider the possibility that the problem is related to `react-native-reanimated`,...
I hope this isn't code that is actually used anywhere. It isn't even valid in strict mode, which is hopefully the default everywhere.
Related to https://github.com/facebook/hermes/issues/1070
This is caused by allocating too many properties for a sparse array. We have a fix in progress.
@robchu05 sorry about that, by bad. I just added that test and apparently our CI didn't flag it as broken on Windows.
This behavior is normal - accessors are slow, because what looks like an ordinary property read has to turn into a function call. This leaves the "fast path" and is...
Different engines have different tradeoffs, but without a speculative JIT (which can speculatively inline the accessor), the pattern is likely to be either similar, or Hermes will be faster in...
Hi, we really need the CLA before we can review it internally. Thanks!
Thank you. A better repro: ```js let buffer = new ArrayBuffer(4); var arrInt = new Int32Array(buffer); var arr32 = new Float32Array(buffer); var a = NaN; arr32[0] = -a; print(arr32[0]); print(arrInt[0].toString(16));...
Is this actually a bug? These seem to be different representations of NaN.