Hello guys, given a function like

suspend fun getThree() = 
  withContext(IO) {
    val one = async { getOne() }
    val two = async { getTwo() }
    
    one.await() + two.await()
  }

would be better to be wrapper in a

coroutineScope

or would the

withContext

be enough?

Hello, Davide using a scope you will be protected against possible leaks, because the scope will be attached to your view/viewmodel lifecycle

withContext

is more to switch between dispatchers

I think it’s wrong explanation from Rafael, in terms of attaching to scope both of them create scope and not different, but withContext also switches scope

using a scope you will be protected against possible leaks

It’s true, but it’s it’s also true for withContext, because with context is create a scope, same as coroutine scope, but also switch dispatcher

Thank you guys 🙂

so you can think about withContext as coroutineScope + context switching

Yes, that absolutely makes sense, should take a look into it! Thanks!