A while ago, when `async` moved into `CoroutineSco...
# ktor
m
A while ago, when
async
moved into
CoroutineScope
, the suggestion was to make functions that needed to use
async
extension methods of
CoroutineScope
. In recent IJ, though, functions that are
suspend
and extension methods of
CoroutineScope
warn about ambiguous coroutine context. I could make functions not extension methods, and wrap each
async
call in
coroutineScope {}
, but I was under the impression that the idea was to share the coroutine scope of the ktor request, and that sprinkling more
coroutineScope
blocks around would be counter to that. What's the current best practice? Sample workload: in ktor request handler, run 2 async tasks concurrently and combine the result.
­čĄö 1