-
Notifications
You must be signed in to change notification settings - Fork 30.3k
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
path: join refactor #25364
path: join refactor #25364
Conversation
ping @nodejs |
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.
I’m afraid I don’t quite understand the purpose of this change. It’s functionally equivalent and doesn’t improve performance. It also makes git blame harder going forward. There is nothing fundamentally wrong with var
.
Hi, @apapirovski! I was just update path join to actually js standards |
@apapirovski Do you feel differently about other refactors to using more modern JS patterns? I’m not happy about the effects on |
@addaleax I’ve blocked most of them when I see them. I think I’ve been reasonably consistent. I’m happy to remove my objection if someone else wants to approve it. |
@apapirovski - pls revisit your position on this PR, in the context of several recent changes in the code base to modernize the variable qualifiers. @Mnwa - can you pls rebase? |
9e5b54a
to
ec96ae7
Compare
@gireeshpunathil Hey! I do it |
But after rebase there is too small changes. I think we can close it becouse someone did a most my changes before |
Change variables init from var to let/const, added destructurization to function arguments and change old
for
to newfor of
Local bench tests join
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes