A modern programming language that makes developers happier.

kotlinlang

How can we use the result of a first routing to call the 2nd one (reformulating my previous question)

you need something like this?

```
suspend fun getFirstResult() : Data? = try {
    getData().await()
} catch(e: Exception) {
    null
}

suspend fun getSecondResult(data: Data) {}

fun getContent() = launch {
    getFirstResult()?.let{ getSecondResult(it) }
}
```

You’d probably want to change `getContent` a bit:
```
fun CoroutineScope.getContent() = async { 
    getFirstResult()?.let { getSecondResult(it) }
}
```

Yea i would probably use async instead of launch

depends on what you want to do, no <@U72C3TBDH>? Example: I call that from my view that does not have any dependency of coroutines or anything like that and in my `getContent` I have at the final a `handleResponse()` to make the communication to my view with states, then my `getContent` needs to launch, or am I missing something?

in my case, i’m showing a spinner when the user taps on a button, it will stay visible until i have the result of the 2nd function

Yes, it depends on the use-case, but the original poster used `async`. And there’s a need of a `CoroutineScope` to call `async` (or `launch`).

Be very very careful using GlobalScope, though.

You lose structured concurrency when using GlobalScope. Let me find the article that explains this (better than discussing it here in a thread)

<https://medium.com/@elizarov/the-reason-to-avoid-globalscope-835337445abc>

this is a good article that talks about it

That one is a great article and this one:
<https://medium.com/@elizarov/structured-concurrency-722d765aa952>

That should not matter. :slightly_smiling_face:

But you can use DI to inject a TestCoroutineScope (or a TestCoroutineDispatcher) for your unit-tests while injecting actual Dispatchers (IO, Default, Main) for your actual app.