Hey guys, where can I read more about this kind of...

# coroutines

[Nikola Milovic]

Hey guys, where can I read more about this kind of behaviour?

fun A() {
B()
C()
}

fun B(){
  scope.launch{
  //call some suspending fun
   }
}

So now C will be executed before B finishes even tho B isn't suspending fun?

[Nikola Milovic]

I need it for an actual usecase. I want to save the progress the user has made before navigating to another screen

binding.exitButton.setOnClickListener {
            autoSave() 
            viewModel.navigateToMainMenu()      
        }

Navigate is a regular function while

fun autoSave() {
        uiScope.launch{
            viewModel.autoSave()
        }
    }

viewModel.autosave is a suspending fun. Now I need it to first save and then proceed to navigate. As now it's not happening in that order

[Marko Novakovic]

@Nikola Milovic why calling uiScope.launch {} in order to call viewModel.autoSave()?

[Marko Novakovic]

everything should go through ViewModel and then you won’t have this kind of problems

[Marko Novakovic]

now, as I can see, you depend on race conditions

[Marko Novakovic]

make ViewModel start a coroutine and when saving work is done emit event to navigate to main menu

[Nikola Milovic]

Thank you @Marko Novakovic

[Marko Novakovic]

@Nikola Milovic you’re welcome

[uli]

No need for events:

binding.exitButton.setOnClickListener {
            uiScope.launch{
                autoSave() 
                viewModel.navigateToMainMenu()
            }     
        }

suspend fun autoSave() {
        viewModel.autoSave()
    }

And depending on the rest of your code you can remove autoSave() (inline it)

[uli]

binding.exitButton.setOnClickListener {
            uiScope.launch{
                viewModel.autoSave() 
                viewModel.navigateToMainMenu()
            }     
        }

[Marko Novakovic]

More of a workaround than a proper solution

[uli]

why would you say that. That’s what coroutines are for. making asynchronous flows linear. Of cause you might want to move the responsibility to the view model.