wait why is this?

# announcements

[Andrew Gazelka]

wait why is this?

[gildor]

Because sequence is syncronous only abstraction

[gildor]

Consumer can use it from non-suspend function

[gildor]

There is no API in sequence to consume values asyncronously

[gildor]

So this is the reason, why only yield suspend function is allowed in sequence builder, to avoid confusion when one may accidentally block caller thread by invoking some arbitrary suspend function

[Andrew Gazelka]

ah ok that makes sense

[gildor]

If you need fully async streams, use kotlinx.coroutines Flow, which may be consumed only from suspend function

[gildor]

Sorry, suspend -> sequence in my first message

[gildor]

Suspend of course asyncronous, but sequence is syncronous, but lazy, same way as Java streams