`uncons` and `concurrently` are not friends
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 2.5k
- Forks
- 636
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 7
Description
... but maybe they can be :) see context in https://github.com/typelevel/fs2/pull/3112#pullrequestreview-1263803863.
One solution I experimented with in https://github.com/typelevel/fs2/pull/3112#issuecomment-1399139450 was when compiling the background stream in concurrently, instead of giving it a new root scope it should derive its scope from the foreground stream.
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 by reading the linked pull request review and issue comment for the context around uncons and concurrently. Inspect how concurrently compiles its background stream and how uncons scopes it; done means the two operations work together without incorrect scope behavior, with coverage for the reported case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- stream-processing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100