softwaremill / softwaremill/ox
Proposal: make forking safe in regard to boundary-based combinators
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 522
- Forks
- 35
- Avg merge
- 45m
- Merged PRs (30d)
- 13
Description
In the future capture calculus will make it possible to prevent unsafe captures of boundary.Label[A] but for now that's not yet stable or even available. I propose that fork family of operators include a scoped token (using a context function) that can be then reused using scala.util.NotGiven to prevent unsafe uses of the api:
Contributor guide
No contributing guide indexed for this repository
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 reviewing pull request #146 and the fork-family operators involving boundary.Label[A]. Trace how the proposed scoped context-function token and scala.util.NotGiven interaction would affect those operators; the issue names no files, tests, or acceptance criteria, so its scope and definition of done need clarification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100