typelevel / typelevel/cats-effect
Introduce an `unyielding { ... }` construct
Open
Nobody has claimed this yet.
:book: laws
: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/2478#issuecomment-982030581. tl;dr, a way to prevent (auto?) cedes/yields for a region of the program.
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 discussion in cats-effect pull request 2478, especially the linked issue comment, to understand the proposed unyielding { ... } semantics. Define the expected behavior for preventing automatic cedes or yields within a region, then use that definition to identify the affected runtime entry points and tests; done means the construct has agreed-upon behavior and coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100