typelevel / typelevel/cats-effect
Experiment with Loom
Open
Nobody has claimed this yet.
:microscope: experiment
- Dominant language
- Scala
- Stars
- 2.2k
- Forks
- 576
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 18
Description
I'm not really sure how feasible it is to run Scala on the Loom Early Access JDK builds, but we should start thinking about what IO would look like in that world. Some questions I'm interested in:
- How necessary is
Asyncgoing to be? - How will Loom virtual threads interact with different forms of tracing? i.e. stack tracing, thread tracing, fiber dumps
- Will a
Fibercorrespond to a Loom virtual thread? - Will we need to support both native platform threads and virtual threads? i.e. should
IOwork seamlessly across different kinds of schedulers
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 files or tests are named. Start by examining how cats-effect's IO, Async, Fiber, tracing, and schedulers relate to Scala on Loom Early Access JDK builds. A useful outcome would be a documented feasibility assessment addressing virtual versus platform threads and the four questions in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- backend, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100