Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

When to use Kotlin suspend keyword?

Tags:

fun startAsyncFunc() {   launch {     asyncFunc1()     asyncFunc2()   } }  fun asyncFunc1() { ... } suspend fun asyncFunc2() { ... } 

I can finish the work without suspend and it even makes test easier (it can be tested without adding runBlocking.

My questions:

  1. asyncFunc1 vs asyncFunc2, which is better and why?
  2. If asyncFunc2 is better, should I always use suspend whenever a function will be ran in the coroutines?

Update

In the recent releases of Kotlin Coroutines, I notice if a method doesn't contain any coroutines code(like launch, async, etc), the compiler complains This inspection reports a suspend modifier as redundant if no other suspend functions are called inside. So I assume that suspend should be only used when it's a must.

Update2

An advice from Google

like image 520
Dewey Reed Avatar asked Feb 06 '19 13:02

Dewey Reed


People also ask

Why do we use Suspend function in Kotlin?

Important: Using suspend doesn't tell Kotlin to run a function on a background thread. It's normal for suspend functions to operate on the main thread. It's also common to launch coroutines on the main thread.

Why use suspend functions?

A suspending function is simply a function that can be paused and resumed at a later time. They can execute a long running operation and wait for it to complete without blocking. The syntax of a suspending function is similar to that of a regular function except for the addition of the suspend keyword.

What is the difference between suspending vs blocking Kotlin?

BLOCKING: Function A has to be completed before Function B continues. The thread is locked for Function A to complete its execution. SUSPENDING: Function A, while has started, could be suspended, and let Function B execute, then only resume later. The thread is not locked by Function A.


2 Answers

You should only declare your function suspend if it needs to. I would say that, when in doubt, if the compiler does not force you, don't use suspend.

Most of the time, if you have a good reason for your function to be suspending, it means it's doing something that probably requires you to call suspending functions like withContext anyway, or it might be a callback based function that you expose as suspending via suspendCoroutine/suspendCancellableCoroutine. Either way calling those functions would force you to declare your own function suspend.

Note that declaring a function suspend does not enable your callers to do anything more than they could when your function was not suspending. If anything, you're limiting the use of your function.

One possible exception to the rule "don't use it unless forced to" would be if you're defining this function as an open method (for instance in an interface) and you expect that some implementations/overrides will need to call suspending functions themselves.

like image 101
Joffrey Avatar answered Oct 06 '22 00:10

Joffrey


suspend keyword means coroutine can be suspended for later execution.

Having said that, you should consciously use it them for coroutines that will get suspended (e.q. your asyncFunc2() made a HTTP call and is awaiting response to process it)

So.

  1. Use suspend for functions that will be delayed in some way (Awaiting some computations, api response etc.)
  2. suspend fun can be run from coroutine only. So, if it gets suspended, it will block the coroutine. Take out the suspend keyword, but run it in coroutine and it will have the same effect. However, if you run this function from outside the coroutine, it will block the thread it was running on.

When testing coroutines, you should always invoke runBlocking. If you don't, a coroutine that gets suspended may not complete, resulting in a failed test.

like image 45
Kuba Pawłowski Avatar answered Oct 06 '22 00:10

Kuba Pawłowski