Skip to content

stream: remove ambiguous code - #29664

Closed
ronag wants to merge 1 commit into
nodejs:masterfrom
nxtedition:stream-eos-dead
Closed

stream: remove ambiguous code#29664
ronag wants to merge 1 commit into
nodejs:masterfrom
nxtedition:stream-eos-dead

Conversation

@ronag

@ronagronag commented Sep 23, 2019

Copy link
Copy Markdown
Member

This cleans up some ambiguous code. I don't believe this actually causes any observable change of behaviour.

writable, readable is supposed to indicate the type of the stream, which does not change... this PR makes the code less confusing

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • documentation is changed or added
  • commit message follows commit guidelines

@mscdex

Copy link
Copy Markdown
Contributor

s/ambigious/ambiguous/ in commit message

@ronagronag changed the title stream: remove ambigious codestream: remove ambiguous codeSep 23, 2019
@ronag

Copy link
Copy Markdown
MemberAuthor

Not sure what you meant. But I'm guess it's the misspelling. Fixed.

@ronag

Copy link
Copy Markdown
MemberAuthor

@mcollina

@mcollinamcollina left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Comment threadlib/internal/streams/end-of-stream.js
Comment threadlib/internal/streams/end-of-stream.js

@mcollinamcollina left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@mcollina

Copy link
Copy Markdown
Member

JungMinu pushed a commit that referenced this pull request Sep 29, 2019
PR-URL: #29664
Reviewed-By: Minwoo Jung <minwoo@nodesource.com>
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
@JungMinu

Copy link
Copy Markdown
Member

Landed in ce62e96

@BridgeARBridgeAR added backport-requested-v12.x stream Issues and PRs related to the stream subsystem. labels Oct 9, 2019
@BridgeAR

Copy link
Copy Markdown
Member

@ronag I guess this depends on other PRs that need backporting first? This currently causes conflicts that are not obvious to resolve. Would you be so kind and check if other PRs need backporting first and add that as well / open a backport if you think that's useful here?

@ronag

ronag commented Oct 9, 2019

Copy link
Copy Markdown
MemberAuthor

This is probably about to be reverted in #29717 (comment).

I will look into backporting this if/when this becomes relevant again.

@MylesBorins

Copy link
Copy Markdown
Contributor

quick ping re: backport

ronag added a commit to nxtedition/node that referenced this pull request Jan 18, 2020
PR-URL: nodejs#29664
Reviewed-By: Minwoo Jung <minwoo@nodesource.com>
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
sxa pushed a commit to sxa/node that referenced this pull request Jan 24, 2020
PR-URL: nodejs#29664
Reviewed-By: Minwoo Jung <minwoo@nodesource.com>
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
@sxa

sxa commented Jan 24, 2020

Copy link
Copy Markdown
Member

@MylesBorins In view of 8c60685#diff-009356850b536cab27b019ba8ad15e72 are you sure this should be backported?

@MylesBorins

Copy link
Copy Markdown
Contributor

Seems like it shouldn't

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

streamIssues and PRs related to the stream subsystem.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants

@ronag@mscdex@mcollina@JungMinu@BridgeAR@MylesBorins@sxa