-
Notifications
You must be signed in to change notification settings - Fork 29.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
internal: changed var to const in linkedlist #8609
Conversation
LGTM |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This may sound a bit crazy, but we may want to benchmark this change. I noticed not too long ago that |
@mscdex if there is anything I can help with let me know. I do not know how to run benchmarks atm so yeah :P |
Ok as far as I can tell, this particular change does not seem to have any measurable negative performance impact, so it should be fine to land. On another positive note, I think I managed to improve |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@AdriVanHoudt ... now that you have a few of these type of PRs in, one thing that would likely be helpful would be to batch multiple commits either into a single PR or even single commit. Doing so makes review a bit easier. |
LGTM. |
@jasnell yeah during the summit the task got divided pretty much by file that's why. Also some changes do entail a lot more (like perf stuff) then I thought so the splitting kinda helped there. I will definitely do more in 1 commit next time! (or do you want me to merge all these together?) |
nah, go ahead and leave these as is. Just wanted to make the suggestion for the future! :-) |
tbh, I’d still prefer 1 commit per file, if only because that may make backporting easier. |
ok, yeah, makes sense. At the very least tho, multiple similar commits per PR. |
Jenkins is kinda hard to navigate so not sure what is failing :S |
… Yeah. New CI, given that #8924 has fixed some of the failures: https://ci.nodejs.org/job/node-test-commit/5455/ |
PR-URL: #8609 Reviewed-By: Brian White <mscdex@mscdex.net> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com>
Landed in b2534f1 |
PR-URL: #8609 Reviewed-By: Brian White <mscdex@mscdex.net> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com>
PR-URL: #8609 Reviewed-By: Brian White <mscdex@mscdex.net> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com>
PR-URL: #8609 Reviewed-By: Brian White <mscdex@mscdex.net> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com>
Checklist
make -j4 test
(UNIX), orvcbuild test nosign
(Windows) passesAffected core subsystem(s)
internal
Description of change
Changed var to const.
Part of nodejs/code-and-learn#56
Refs: #8410