typelevel / typelevel/cats-effect
Avoid per-iteration read barriers in worker loop
Open
Nobody has claimed this yet.
:mushroom: enhancement
- Dominant language
- Scala
- Stars
- 2.2k
- Forks
- 576
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 18
Description
Spinning out of https://github.com/typelevel/cats-effect/pull/3499#discussion_r1170622173. These are the ones I'm aware of:
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 discussion linked from the issue, then inspect the two referenced sections in core/jvm/src/main/scala/cats/effect/unsafe/WorkerThread.scala at lines 419 and 689–694. Determine how the worker loop currently performs its read barriers and identify all per-iteration cases covered by the issue. Done means the listed barriers are no longer performed per iteration while the worker loop's behavior remains correct.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- backend, performance
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100