Show this thread
-
I imagine the separate integer exponentiation routine was hand-written for performance gains over calling `Math.pow` in certain scenarios
Show this thread
-
-
-
For future reference I'm seeing this in 64-bit Chrome 72.0.3626.96 on Windows, and in Node.js 10.15.1 which uses V8 6.8.275.32-node.12
Show this thread -
Reportedly a long-known issue with a fix on its way down the pipelinehttps://twitter.com/mathias/status/1094209241311838210 …
Show this thread -
New conversation -
-
-
-
Simpler repro: const x = 99; console.log(x ** x - 99 ** 99); It’s fixed in
@v8js master. See https://bugs.chromium.org/p/v8/issues/detail?id=5848 …. - 4 more replies
New conversation -
-
-
I noticed the other day when I was practicing recursions and wrote my own version of pow and was getting some odd false negatives (also on Node.js).
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Typo’d this in dev tools, causing an infinite loop. Closed the tab, but next thing I know the fans are spinning. Got it right, ended at 8939. Tried again, got 13408.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
W the actual f
-
v8 optimizes number operations in a different way than the actual Javascript operator. So x**x!=99*99 due to that bug. As the loop is being executed a lot, v8 optimizes the loop and now it realizes x**x is actually 99**99 so basically you get out i = how long before v8 optimizes.
End of conversation
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.