resuming a topic that has been discussed for a whi...

# coroutines

[acando86]

resuming a topic that has been discussed for a while in this chat during the previous days, and that seems to be a source of confusion sometimes, i would love to see at some point some official tips & hints on idiomatic patterns and ways to deal with exceptions when using coroutines after structured concurrency.. there're plenty of combinations (eg, job vs supervisor when constructing the coroutine scope, different launchers as entry point for coroutines, and of course suspend functions themselves) and it might be confusing at first to get the pros and cons, implications and potential antipatterns of the different strategies and choices.. the documentation focus often on the happy path and the general idea of what happens in case of exception, but I see that sometimes there are still some confusion around exceptions flows and how to use them effectively and safely in the context of structured concurrency, and how they are actually meant to be used. I think it's important in order to get the best out of structured concurrency instead of falling into antipatterns.