Skip to content

Conversation

@achingbrain
Copy link
Member

Adds a guard to the .close operation similar to the one on .abort that ensures we only close the stream if it is open.

The individual .closeRead/.closeWrite operations already guard on the read/write status of the stream so there's no functional change, we just avoid a bit more async work as those methods return promises.

Change checklist

  • I have performed a self-review of my own code
  • I have made corresponding changes to the documentation if necessary (this includes comments as well)
  • I have added tests that prove my fix is effective or that my feature works

Adds a guard to the `.close` operation similar to the one on
`.abort` that ensures we only close the stream if it is open.

The individual `.closeRead`/`.closeWrite` operations already guard
on the read/write status of the stream so there's no functional
change, we just avoid a bit more async work as those methods
return promises.
@achingbrain achingbrain requested a review from a team as a code owner November 15, 2024 12:06
@achingbrain achingbrain merged commit 3098232 into main Nov 15, 2024
@achingbrain achingbrain deleted the fix/only-close-stream-if-open branch November 15, 2024 16:24
@achingbrain achingbrain mentioned this pull request Nov 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants