Uh oh!
There was an error while loading. Please reload this page.
wasi: refactor to avoid unsafe array iteration - #36724
Conversation
Trott
left a comment
There was a problem hiding this comment.
I might be telling you something you already know, but in the past, we've used for rather than .forEach() for performance purposes. I don't think either of these are hot paths, so it's probably fine. @nodejs/wasi
aduh95
commented
Jan 2, 2021
I'm running benchmarks on my other PRs with changes similar to this one, so far I haven't hit an perf issue. My guess is that both approaches are equivalent, but we can use a |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
nodejs-github-bot
commented
Jan 5, 2021
PR-URL: nodejs#36724 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com>
f553c8e to
08d8958Compareaduh95
commented
Jan 6, 2021
Landed in 08d8958 |
PR-URL: #36724 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com>
PR-URL: #36724 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com>
PR-URL: #36724 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com>
PR-URL: #36724 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com>
Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passes