Avoid triggering stdio streams creation #101
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This breaks API and encumbers the ability to pass arbitrary streams for evaluation. I'm pretty against this as-is. Is there a way to achieve this otherwise? |
|
@Qix- It is supposed to be internal only fix, without any changes to API. Am I missing something there? |
|
Nvm I see now. LGTM. |
Qix-
approved these changes
Jul 22, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Use
ttyinstead of stdio streams to detect if stdio outputs are ttys to improve require speed.ttyis used by stdio streams, so if streams are initialized later or were initialized before there will be no overhead. However if streams are not used(process.stdoutandprocess.stderrstream objects, not OS streams itself), it speeds up require times slightly.