stream.Transform should avoid writable state
Open
Nobody has claimed this yet.
benchmark-needed
- Dominant language
- Shell
- Stars
- 399
- Forks
- 11
- Avg merge
- 29m
- Merged PRs (30d)
- 1
Description
stream.Transform is currently implemented as a Duplex which has both a writable and readable side, this causes unnecessary overhead and buffering. Instead, stream.Transform should inherit the implementation of stream.Readable while also implementing the interface of stream.Writable
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named. Start by locating the stream.Transform implementation and its Duplex, Readable, and Writable relationships, then inspect existing stream tests and performance measurements. Done means Transform uses the Readable implementation, exposes the Writable interface, and avoids the unnecessary writable-side overhead and buffering described here.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100