Instead of

val task = async(ioContext) { dataProvider.loadData("Task") }
    val result: Result<String> = task.await()

you can use

val result: Result<String>  = run(ioContext) { dataProvider.loadData("Task") }

You can also use Sealed classes to implement

Result

with better and API and avoid nullable fields

As for sealed class, in this case I will have to make Success class generic.

So instead if nullability check I will end up with type check (is Success, is Error)

And about run. I don't like using it, because if you wrap run with try-cath, cancel job, code inside run can still crash your app.

because your app still crashes on

async.await()

call, I don’t see difference with

run

in your example

But you can have Sealed with generic - https://github.com/gildor/kotlin-coroutines-retrofit/blob/master/src/main/kotlin/ru/gildor/coroutines/retrofit/Result.kt#L10 I think Sealed class is better not because use type check instead of null check, but because you can pass this Result class of particular type or save it to (for example you can have something like

fun processError(result: Result.Error)

. Also, you can have more complicated Sealed class with additional helper methods and combinators.

run doesn’t have default dispatcher

I will check your example later when will have time

oh, you are right about default context, you still should pass it, otherwise there is no reason to use run

but still not sure why you have this error with cancelled run, should check