-
Notifications
You must be signed in to change notification settings - Fork 30.1k
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
child_process: refactor internal/child_process.js #11366
Conversation
lib/internal/child_process.js
Outdated
stream.resume(); | ||
}); | ||
if (subprocess.stdio === null || subprocess.stdio === undefined) return; | ||
for (let i = 0; i < subprocess.stdio.length; i++) { |
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.
Use var
instead of let
here for better backportability (let
used in this way is still slower at least in v6.x and v4.x).
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.
This suggestion goes for all of the other occurrences below too.
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.
OK! Is there a guide on code style?
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.
@notarseniy make lint
should have reported that issue. make lint
is part of make test
so if you ran tests, that should have come up as a lint error after the tests all passed. If the linter didn't report it, then there is probably a bug in our custom lint rule.
lib/internal/child_process.js
Outdated
return; | ||
stream.resume(); | ||
}); | ||
if (subprocess.stdio === null || subprocess.stdio === undefined) return; |
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 not sure this change is really worth it, the previous conditional is shorter and is equivalent in behavior.
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.
Motivation of this change was this line with 'that-style' condition.
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.
Well IMHO that other line could/should be changed to a non-strict equality check. The performance difference probably isn't measurable anymore.
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.
Ok!
lib/internal/child_process.js
Outdated
}); | ||
if (subprocess.stdio === null || subprocess.stdio === undefined) return; | ||
for (let i = 0; i < subprocess.stdio.length; i++) { | ||
if (!subprocess.stdio[i] || !subprocess.stdio[i].readable || subprocess.stdio[i]._readableState.readableListening) |
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.
Instead of looking up the value each time, add a temporary variable before the conditional. For example:
const stdio = subprocess.stdio;
for (var i = 0; i < stdio.length; ++i) {
const stream = stdio[i];
// .... keep rest of the code the same
}
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.
This suggestion goes for all of the other occurrences below too.
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.
Yeah, sounds good. Will fix this
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.
Good comment. Will fix.
@@ -800,7 +800,7 @@ function _validateStdio(stdio, sync) { | |||
stdio = i < 3 ? 'pipe' : 'ignore'; | |||
} | |||
|
|||
if (stdio === null || stdio === 'ignore') { | |||
if (stdio === 'ignore') { |
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.
Why this change? This would change behavior...
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.
In previous condition we're handling stdio === null
, so this condition never will be executed with stdio === null
03eba26
to
0b3efdc
Compare
Commited with fixes of comments. |
More linting issues it seems. Run I'm guessing it's due to the duplicate |
lib/internal/child_process.js
Outdated
return; | ||
if (subprocess.stdio === null || subprocess.stdio === undefined) return; | ||
|
||
const stdio = subprocess.stdio; |
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.
This could probably be moved to the top of the function, where the first conditional can take advantage of it.
0b3efdc
to
9bfcaf4
Compare
* Prefer === to == where possible * Remove condition that will always be false * Prefer for-loop statements to forEach where possible for perfomance reasons
9bfcaf4
to
efaa7d7
Compare
CI is green. LGTM. |
Bump! 😅 What the status of PR? Any other comments or additions? |
* Prefer === to == where possible * Remove condition that will always be false * Prefer for-loop statements to forEach where possible for perfomance reasons PR-URL: #11366 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Sam Roberts <vieuxtech@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Brian White <mscdex@mscdex.net>
@notarseniy I think it has just been forgotten. I went ahead and landed it in 8fc362e. Thanks for the contribution! |
Thats okay :) Thank you too! |
* Prefer === to == where possible * Remove condition that will always be false * Prefer for-loop statements to forEach where possible for perfomance reasons PR-URL: #11366 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Sam Roberts <vieuxtech@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Brian White <mscdex@mscdex.net>
* Prefer === to == where possible * Remove condition that will always be false * Prefer for-loop statements to forEach where possible for perfomance reasons PR-URL: #11366 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Sam Roberts <vieuxtech@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Brian White <mscdex@mscdex.net>
* Prefer === to == where possible * Remove condition that will always be false * Prefer for-loop statements to forEach where possible for perfomance reasons PR-URL: #11366 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Sam Roberts <vieuxtech@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Brian White <mscdex@mscdex.net>
* Prefer === to == where possible * Remove condition that will always be false * Prefer for-loop statements to forEach where possible for perfomance reasons PR-URL: #11366 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Sam Roberts <vieuxtech@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Brian White <mscdex@mscdex.net>
* Prefer === to == where possible * Remove condition that will always be false * Prefer for-loop statements to forEach where possible for perfomance reasons PR-URL: #11366 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Sam Roberts <vieuxtech@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Brian White <mscdex@mscdex.net>
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passesAffected core subsystem(s)
child_process