Hi, I'm new to coroutines and I would appreciate some clarification. I'm following different examples of basic coroutines and I'm seeing these two ways of structuring the code. What are the differences, pros and cons of them? Suspend funs to call:

suspend fun foo1() // function
suspend fun foo2() // function

First approach:

// sequential code

viewModelScope.launch { foo1() }

// more sequential code

viewModelScope.launch { foo2() }

// more sequential code}

Second approach:

viewModelScope.launch {
	// sequential code

	foo1()

	// more sequential code

	foo2()

	// more sequential code
}

I've also saw this second approach with

async

calls inside the main

launch

one. Thanks!

First approach is not sequential, you launched two asynchronous coroutines, foo1 and foo2 will run concurrently

This is probably the best resource I could give you to understand the difference, and when to use which : https://kotlinlang.org/docs/composing-suspending-functions.html#sequential-by-default

Thank you. I meant that before, between and after foo calls there are code not related with

suspend

functions

@AdalPari Wow, looks like the new Kotlin docs are not properly linked yet. Here is a working link : https://kotlinlang.org/docs/reference/coroutines/composing-suspending-functions.html

Thanks!