Skip to content
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Commit 015180d

Browse files
authoredJun 5, 2022
Update 2022_06_05_structured-concurrency-scala-future.md
1 parent dec56ff commit 015180d

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed
 

‎2022_06_05_structured-concurrency-scala-future.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -116,7 +116,7 @@ Here are implementations of two subsets:
116116

117117
### Why I'm writing this now:
118118

119-
Currently, this is just a [directory]((https://github.com/rssh/dotty-cps-async/tree/master/jvm/src/test/scala/futureScope) inside JVM tests in dotty-cps-async. To make this a usable library, we need to do some work: document API, add tests, implement obvious extensions, port to js/native, etc.
119+
Currently, this is just a [directory](https://github.com/rssh/dotty-cps-async/tree/master/jvm/src/test/scala/futureScope) inside JVM tests in dotty-cps-async. To make this a usable library, we need to do some work: document API, add tests, implement obvious extensions, port to js/native, etc.
120120
Also exists a set of choices, which can be configured and is interesting to discuss:
121121
- should we cancel() child context implicitly (as now), or join or ask user finish with cancel or join ?
122122
- should we propagate exceptions or leave this duty to the user and issue a warning when see possible unhandled exception?

0 commit comments

Comments
 (0)
Please sign in to comment.