3 ms·
In the final example where he switches to int32 for Go (after "Let's make it use int32 consistently and try again"), he runs gopherjs twice instead of running g
by pauljz 11y ago
In the final example where he switches to int32 for Go (after "Let's make it use int32 consistently and try again"), he runs gopherjs twice instead of running go and gopherjs. I hope that's a typo.
The reasoning seems correct, but it'd be nice to have the benchmarks corrected to verify.
- shurcooL 11y agoIt is indeed a typo, sorry about that! I've fixed it [1] after confirming [2] (yet again just now; I've ran those numbers many many times so I'm very confident it's not a one time fluke). Thanks for catching it. You're also welcome to try to confirm the results yourself, they should be reproducible! [1] https://github.com/gopherjs/gopherjs.github.io/commit/acea7a862c161796697aed812d9142945d09d1e8#commitcomment-13497916 https://github.com/gopherjs/gopherjs.github.io/commit/acea7a... [2] https://gist.github.com/shurcooL/02183a57c51b28eaadf4 https://gist.github.com/shurcooL/02183a57c51b28eaadf4