ARCHIVED: This has been moved into Arrow
Cont<R, A> represents a function of suspend () -> A that can fail with R (and Throwable), so it's defined
by suspend fun <B> fold(f: suspend (R) -> B, g: suspend (A) -> B): B.
So to construct a Cont<R, A> we simply call the cont<R, A> { } DSL, which exposes a rich syntax through the lambda
receiver suspend ContEffect<R>.() -> A.
What is interesting about the Cont<R, A> type is that it doesn't rely on any wrappers such as Either, Ior
or Validated. Instead Cont<R, A> represents a suspend function, and only when we call fold it will actually create
a Continuation and runs the computation (without intercepting).
This makes Cont<R, A> a very efficient generic runtime.
Let's write a small program to read a file from disk, and instead of having the program work exception based we want to turn it into a polymorphic type-safe program.
We'll start by defining a small function that accepts a String, and does some simply validation to check that the path
is not empty. If the path is empty, we want to program to result in EmptyPath. So we're immediately going to see how
we can raise an error of any arbitrary type R by using the function shift. The name shift comes shifting (or
changing, especially unexpectedly), away from the computation and finishing the Continuation with R.
object EmptyPath
fun readFile(path: String): Cont<EmptyPath, Unit> = cont {
if (path.isEmpty()) shift(EmptyPath) else Unit
}Here we see how we can define a Cont<R, A> which has EmptyPath for the shift type R, and Unit for the success
type A.
Patterns like validating a Boolean is very common, and the Cont DSL offers utility functions like kotlin.require
and kotlin.requireNotNull. They're named ensure and ensureNotNull to avoid conflicts with the kotlin namespace.
So let's rewrite the function from above to use the DSL instead.
fun readFile2(path: String?): Cont<EmptyPath, Unit> = cont {
ensureNotNull(path) { EmptyPath }
ensure(path.isEmpty()) { EmptyPath }
}You can get the full code here.
Now that we have the path, we can read from the File and return it as a domain model Content.
We also want to take a look at what exceptions reading from a file might occur FileNotFoundException & SecurityError,
so lets make some domain errors for those too. Grouping them as a sealed interface is useful since that way we can resolve all errors in a type safe manner.
@JvmInline
value class Content(val body: List<String>)
sealed interface FileError
@JvmInline value class SecurityError(val msg: String?) : FileError
@JvmInline value class FileNotFound(val path: String) : FileError
object EmptyPath : FileError {
override fun toString() = "EmptyPath"
}We can finish our function, but we need to refactor our return value from Unit to Content and our error type from EmptyPath to FileError.
fun readFile(path: String?): Cont<FileError, Content> = cont {
ensureNotNull(path) { EmptyPath }
ensure(path.isNotEmpty()) { EmptyPath }
try {
val lines = File(path).readLines()
Content(lines)
} catch (e: FileNotFoundException) {
shift(FileNotFound(path))
} catch (e: SecurityException) {
shift(SecurityError(e.message))
}
}The readFile function defines a suspend fun that will return:
- the
Contentof a givenpath - a
FileError - An unexpected fatal error (
OutOfMemoryException)
Since these are the properties of our Cont function, we can turn it into a value.
suspend fun test() {
readFile("").toEither() shouldBe Either.Left(EmptyPath)
readFile("knit.properties").toValidated() shouldBe Validated.Invalid(FileNotFound("knit.properties"))
readFile("gradle.properties").toIor() shouldBe Ior.Left(FileNotFound("gradle.properties"))
readFile("README.MD").toOption { None } shouldBe None
readFile("build.gradle.kts").fold({ _: FileError -> null }, { it })
.shouldBeInstanceOf<Content>()
.body.shouldNotBeEmpty()
}You can get the full code here.
The functions above our available out of the box, but it's easy to define your own extension functions in terms
of fold. Implementing the toEither() operator is as simple as:
suspend fun <R, A> Cont<R, A>.toEither(): Either<R, A> =
fold({ Either.Left(it) }) { Either.Right(it) }
suspend fun <A> Cont<None, A>.toOption(): Option<A> =
fold(::identity) { Some(it) }You can get the full code here.
Adding your own syntax to ContEffect<R> is tricky atm, but will be easy once "Multiple Receivers" become available.
context(ContEffect<R>)
suspend fun <R, A> Either<R, A>.bind(): A =
when (this) {
is Either.Left -> shift(value)
is Either.Right -> value
}
context(ContEffect<None>)
fun <A> Option<A>.bind(): A =
fold({ shift(it) }, ::identity)
Handling errors of type R is the same as handling errors for any other data type in Arrow.
Cont<R, A> offers handleError, handleErrorWith, redeem, redeemWith and attempt.
As you can see in the examples below it is possible to resolve errors of R or Throwable in Cont<R, A> in a generic manner.
There is no need to run Cont<R, A> into Either<R, A> before you can access R,
you can simply call the same functions on Cont<R, A> as you would on Either<R, A> directly.
val failed: Cont<String, Int> =
cont { shift("failed") }
val resolved: Cont<Nothing, Int> =
failed.handleError { it.length }
val newError: Cont<List<Char>, Int> =
failed.handleErrorWith { str ->
cont { shift(str.reversed().toList()) }
}
val redeemed: Cont<Nothing, Int> =
failed.redeem({ str -> str.length }, ::identity)
val captured: Cont<String, Result<Int>> = cont<String, Int> {
1
}.attempt()
suspend fun test() {
failed.toEither() shouldBe Either.Left("failed")
resolved.toEither() shouldBe Either.Right(6)
newError.toEither() shouldBe Either.Left(listOf('d', 'e', 'l', 'i', 'a', 'f'))
redeemed.toEither() shouldBe Either.Right(6)
captured.toEither() shouldBe Either.Right(Result.success(1))
}You can get the full code here.
Note:
Handling errors can also be done with try/catch but this is not recommended, it uses CancellationException which is used to cancel Coroutines and is advised not to capture in Kotlin.
The CancellationException from Cont is ShiftCancellationException, this a public type so it can be distinguished from any other CancellationException if necessary.
Cont<R, A> relies on kotlin.cancellation.CancellationException to shift error values of type R inside the Continuation since it effectively cancels/short-circuits it.
For this reason shift adheres to the same rules as Structured Concurrency
Let's overview below how shift behaves with the different concurrency builders from Arrow Fx & KotlinX Coroutines.
In the examples below we're going to be using a utility to show how sibling tasks get cancelled.
The utility function show below called awaitExitCase will never finish suspending, and completes a Deferred with the ExitCase.
ExitCase is a sealed class that can be a value of Failure(Throwable), Cancelled(CancellationException), or Completed.
Since awaitExitCase suspends forever, it can only result in Cancelled(CancellationException).
suspend fun <A> awaitExitCase(exit: CompletableDeferred<ExitCase>): A =
guaranteeCase(::awaitCancellation) { exitCase -> exit.complete(exitCase) }All operators in Arrow Fx Coroutines run in place, so they have no way of leaking shift.
It's there always safe to compose cont with any Arrow Fx combinator. Let's see some small examples below.
suspend fun test() = checkAll(Arb.string()) { error ->
val exit = CompletableDeferred<ExitCase>()
cont<String, Int> {
parZip({ awaitExitCase<Int>(exit) }, { shift<Int>(error) }) { a, b -> a + b }
}.fold({ it shouldBe error }, { fail("Int can never be the result") })
exit.await().shouldBeTypeOf<ExitCase>()
}You can get the full code here. [comment]: <> (Test disabled due to missing join in parZip)
suspend fun test() = checkAll(Arb.string()) { error ->
val exits = (0..3).map { CompletableDeferred<ExitCase>() }
cont<String, List<Unit>> {
(0..4).parTraverse { index ->
if (index == 4) shift(error)
else awaitExitCase(exits[index])
}
}.fold({ msg -> msg shouldBe error }, { fail("Int can never be the result") })
// It's possible not all parallel task got launched, and in those cases awaitCancellation never ran
exits.forEach { exit -> exit.getOrNull()?.shouldBeTypeOf<ExitCase.Cancelled>() }
}parTraverse will launch 5 tasks, for every element in 1..5.
The last task to get scheduled will shift with "error", and it will cancel the other launched tasks before returning.
You can get the full code here.
suspend fun test() = checkAll(Arb.string()) { error ->
val exit = CompletableDeferred<ExitCase>()
cont<String, Int> {
raceN({ awaitExitCase<Int>(exit) }) { shift<Int>(error) }
.merge() // Flatten Either<Int, Int> result from race into Int
}.fold({ msg -> msg shouldBe error }, { fail("Int can never be the result") })
// It's possible not all parallel task got launched, and in those cases awaitCancellation never ran
exit.getOrNull()?.shouldBeTypeOf<ExitCase.Cancelled>()
}raceN races n suspend functions in parallel, and cancels all participating functions when a winner is found.
We can consider the function that shifts the winner of the race, except with a shifted value instead of a successful one.
So when a function in the race shifts, and thus short-circuiting the race, it will cancel all the participating functions.
You can get the full code here.
suspend fun test() = checkAll(Arb.string()) { error ->
val exit = CompletableDeferred<ExitCase>()
cont<String, Int> {
bracketCase(
acquire = { File("build.gradle.kts").bufferedReader() },
use = { reader: BufferedReader -> shift(error) },
release = { reader, exitCase ->
reader.close()
exit.complete(exitCase)
}
)
}.fold({ it shouldBe error }, { fail("Int can never be the result") })
exit.await().shouldBeTypeOf<ExitCase.Cancelled>()
}You can get the full code here.
suspend fun test() = checkAll(Arb.string()) { error ->
val exit = CompletableDeferred<ExitCase>()
fun bufferedReader(path: String): Resource<BufferedReader> =
Resource.fromAutoCloseable { File(path).bufferedReader() }
.releaseCase { _, exitCase -> exit.complete(exitCase) }
cont<String, Int> {
val lineCount = bufferedReader("build.gradle.kts")
.use { reader -> shift<Int>(error) }
lineCount
}.fold({ it shouldBe error }, { fail("Int can never be the result") })
exit.await().shouldBeTypeOf<ExitCase.Cancelled>()
}You can get the full code here.
It's always safe to call shift from withContext since it runs in place, so it has no way of leaking shift.
When shift is called from within withContext it will cancel all Jobs running inside the CoroutineScope of withContext.
suspend fun test() {
val exit = CompletableDeferred<ExitCase>()
cont<FileError, Int> {
withContext(Dispatchers.IO) {
val job = launch { awaitExitCase(exit) }
val content = readFile("failure").bind()
job.join()
content.body.size
}
}.fold({ e -> e shouldBe FileNotFound("failure") }, { fail("Int can never be the result") })
exit.await().shouldBeInstanceOf<ExitCase>()
}You can get the full code here.
When calling shift from async you should always call await, otherwise shift can leak out of its scope.
suspend fun test() = checkAll(Arb.string(), Arb.string()) { errorA, errorB ->
coroutineScope {
cont<String, Int> {
val fa = async<Int> { shift(errorA) }
val fb = async<Int> { shift(errorB) }
fa.await() + fb.await()
}.fold({ error -> error shouldBeIn listOf(errorA, errorB) }, { fail("Int can never be the result") })
}
}You can get the full code here.
suspend fun test() = checkAll(Arb.string(), Arb.string(), Arb.int()) { errorA, errorB, int ->
cont<String, Int> {
coroutineScope<Int> {
launch { shift(errorA) }
launch { shift(errorB) }
int
}
}.fold({ fail("Shift can never finish") }, { it shouldBe int })
}You can get the full code here.
NOTE
Capturing shift into a lambda, and leaking it outside of Cont to be invoked outside will yield unexpected results.
Below we capture shift from inside the DSL, and then invoke it outside its context ContEffect<String>.
cont<String, suspend () -> Unit> {
suspend { shift("error") }
}.fold({ }, { leakedShift -> leakedShift.invoke() })The same violation is possible in all DSLs in Kotlin, including Structured Concurrency.
val leakedAsync = coroutineScope<suspend () -> Deferred<Unit>> {
suspend {
async {
println("I am never going to run, until I get called invoked from outside")
}
}
}
leakedAsync.invoke().await()