fix: use NullOutputStream.NULL_OUTPUT_STREAM rather than NullOutputStream.INSTANCE #256
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
…ream.INSTANCE Fixes an issue I was encountering where NullOutputStream.INSTANCE did not exist - unsure why it did not, but this change doesn't change anything since INSTANCE and NULL_OUTPUT_STREAM are the same, and other parts of the code base already use NULL_OUTPUT_STREAM
|
Also faced with this issue, are there any workarounds? |
shedaniel
approved these changes
Dec 24, 2024
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.
Fixes an issue I was encountering where
NullOutputStream.INSTANCEdid not exist - unsure why it did not, but this change doesn't change anything sinceINSTANCEandNULL_OUTPUT_STREAMare equivalent. Other parts of the code base already use NULL_OUTPUT_STREAM