Reimplement `Channel` in terms of `Queue`
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 2.5k
- Forks
- 636
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 7
Description
It's very unclear that Channel is actually meaningfully faster than an implementation based directly on Cats Effect's Queue. More importantly, since Queue is now being optimized substantially, Channel should probably lean on that primitive rather than its own data structures so as to inherit the performance gains. This will be particularly dramatic when typelevel/cats-effect#2890 is completed (which will be during the 3.4.x series, and possibly 3.4.0).
A simple strawman implementation of Channel (which is probably at least close to functional) can be found in this gist: https://gist.github.com/djspiewak/847532614a166af9f811e972d6f2c36f
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
Start with the linked strawman implementation and compare its Channel design with the existing Queue and Channel code. Determine how the reimplementation should preserve Channel behavior while delegating to Queue, then validate that the resulting implementation inherits the intended Queue performance improvements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- stream-processing
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100