Hi, if I for loops async { }, is there a guarantee of order of them starting to run? I have a semaph...

# coroutines

[ursus]

Hi, if I for loops async { }, is there a guarantee of order of them starting to run? I have a semaphore inside them, but it seems race-y

[octylFractal]

No, I don't think there is a guaranteed order

[Zach Klippenstein (he/him) [MOD]]

Nope, there is no ordering guarantee. If you need explicit ordering though, you can implement it manually.

[ursus]

Ok makes sense, how would I go about doing that? Blocking queue?

[Zach Klippenstein (he/him) [MOD]]

If by “blocking queue” you mean Channel, then yes, that’s one way 😉

[Zach Klippenstein (he/him) [MOD]]

(Channel is effectively a blocking suspending queue)

[ursus]

sorry im coroutine newb. Ive seen channels used to pipe data, but it seems I want to pipe lazy Deffered instances and start them in the receiver?

[Zach Klippenstein (he/him) [MOD]]

You could do that, or you could just send suspend functions through your channel directly, and have your receiver do the async part

[ursus]

hm, but doesnt that make the start of the async race-y again?

[Zach Klippenstein (he/him) [MOD]]

true. start = UNDISPATCHED might be better here, no channel required,

[ursus]

interesting, the way I read the docs is the async body going to actually get executed synchronously until first susp. point, correct?you think I can rely on that?

[Zach Klippenstein (he/him) [MOD]]

yep