as someone who hasn't gotten into coroutines at all yet, i'd recommend putting in a comparison of how this is executed and used as well.

The usage is similar, it has similar functionality. api is different and that is what I tried to emphasize

you only really show where they can be useful but nothing about usage

I will try to give some more context

well just more details, like communication between coroutines and stuff like blocking vs no blocking ones

it seems your target audience is someone who doesn't know much about coroutines or when/how to use them, and then you only show half of how to use them. I'm only going to write this part of the code once, but i'm going to have to use this function many times. Showing that its both easier to write/understand on the implementation side AND easier to write/understand on the calling side is important to someone who doesn't know anything about coroutines

i am new to them, but am assuming suspend in the method def is similar to await of other langauges

Thanks, I added some more context at the beginning, hope it helps. generally, I wanted to focus on the implementation and not the usage. However, I will also add some references to how coroutines work.

@oshai it is totally unclear why you need some suspend/async calls here

ok, I will try to clear that up as well