https://kotlinlang.org logo
Channels
100daysofcode
100daysofkotlin
100daysofkotlin-2021
advent-of-code
aem
ai
alexa
algeria
algolialibraries
amsterdam
android
android-architecture
android-databinding
android-studio
androidgithubprojects
androidthings
androidx
androidx-xprocessing
anime
anko
announcements
apollo-kotlin
appintro
arabic
argentina
arkenv
arksemdevteam
armenia
arrow
arrow-contributors
arrow-meta
ass
atlanta
atm17
atrium
austin
australia
austria
awesome-kotlin
ballast
bangladesh
barcelona
bayarea
bazel
beepiz-libraries
belgium
benchmarks
berlin
big-data
books
boston
brazil
brikk
budapest
build
build-tools
bulgaria
bydgoszcz
cambodia
canada
carrat
carrat-dev
carrat-feed
chicago
chile
china
chucker
cincinnati-user-group
cli
clikt
cloudfoundry
cn
cobalt
code-coverage
codeforces
codemash-precompiler
codereview
codingame
codingconventions
coimbatore
collaborations
colombia
colorado
communities
competitive-programming
competitivecoding
compiler
compose
compose-android
compose-desktop
compose-hiring
compose-ios
compose-mp
compose-ui-showcase
compose-wear
compose-web
confetti
connect-audit-events
corda
cork
coroutines
couchbase
coursera
croatia
cryptography
cscenter-course-2016
cucumber-bdd
cyprus
czech
dagger
data2viz
databinding
datascience
dckotlin
debugging
decompose
decouple
denmark
deprecated
detekt
detekt-hint
dev-core
dfw
docs-revamped
dokka
domain-driven-design
doodle
dsl
dublin
dutch
eap
eclipse
ecuador
edinburgh
education
effective-kotlin
effectivekotlin
emacs
embedded-kotlin
estatik
event21-community-content
events
exposed
failgood
fb-internal-demo
feed
firebase
flow
fluid-libraries
forkhandles
forum
fosdem
fp-in-kotlin
framework-elide
freenode
french
fritz2
fuchsia
functional
funktionale
gamedev
ge-kotlin
general-advice
georgia
geospatial
german-lang
getting-started
github-workflows-kt
glance
godot-kotlin
google-io
gradle
graphic
graphkool
graphql
graphql-kotlin
graviton-browser
greece
grpc
gsoc
gui
hackathons
hacktoberfest
hamburg
hamkrest
helios
helsinki
hexagon
hibernate
hikari-cp
hire-me
hiring
hongkong
hoplite
http4k
hungary
hyderabad
image-processing
india
indonesia
inkremental
intellij
intellij-plugins
intellij-tricks
internships
introduce-yourself
io
ios
iran
israel
istanbulcoders
italian
jackson-kotlin
jadx
japanese
jasync-sql
java-to-kotlin-refactoring
javadevelopers
javafx
javalin
javascript
jdbi
jhipster-kotlin
jobsworldwide
jpa
jshdq
juul-libraries
jvm-ir-backend-feedback
jxadapter
k2-early-adopters
kaal
kafka
kakao
kalasim
kapt
karachi
karg
karlsruhe
kash_shell
kaskade
kbuild
kdbc
kgen-doc-tools
kgraphql
kinta
klaxon
klock
kloudformation
kmdc
kmm-español
kmongo
knbt
knote
koalaql
koans
kobalt
kobweb
kodein
kodex
kohesive
koin
koin-dev
komapper
kondor-json
kong
kontent
kontributors
korau
korean
korge
korim
korio
korlibs
korte
kotest
kotest-contributors
kotless
kotlick
kotlin-asia
kotlin-beam
kotlin-by-example
kotlin-csv
kotlin-data-storage
kotlin-foundation
kotlin-fuel
kotlin-in-action
kotlin-inject
kotlin-latam
kotlin-logging
kotlin-multiplatform-contest
kotlin-mumbai
kotlin-native
kotlin-pakistan
kotlin-plugin
kotlin-pune
kotlin-roadmap
kotlin-samples
kotlin-sap
kotlin-serbia
kotlin-spark
kotlin-szeged
kotlin-website
kotlinacademy
kotlinbot
kotlinconf
kotlindl
kotlinforbeginners
kotlingforbeginners
kotlinlondon
kotlinmad
kotlinprogrammers
kotlinsu
kotlintest
kotlintest-devs
kotlintlv
kotlinultimatechallenge
kotlinx-datetime
kotlinx-files
kotlinx-html
kotrix
kotson
kovenant
kprompt
kraph
krawler
kroto-plus
ksp
ktcc
ktfmt
ktlint
ktor
ktp
kubed
kug-leads
kug-torino
kvision
kweb
lambdaworld_cadiz
lanark
language-evolution
language-proposals
latvia
leakcanary
leedskotlinusergroup
lets-have-fun
libgdx
libkgd
library-development
lincheck
linkeddata
lithuania
london
losangeles
lottie
love
lychee
macedonia
machinelearningbawas
madrid
malaysia
mathematics
meetkotlin
memes
meta
metro-detroit
mexico
miami
micronaut
minnesota
minutest
mirror
mockk
moko
moldova
monsterpuzzle
montreal
moonbean
morocco
motionlayout
mpapt
mu
multiplatform
mumbai
munich
mvikotlin
mvrx
myndocs-oauth2-server
naming
navigation-architecture-component
nepal
new-mexico
new-zealand
newname
nigeria
nodejs
norway
npm-publish
nyc
oceania
ohio-kotlin-users
oldenburg
oolong
opensource
orbit-mvi
osgi
otpisani
package-search
pakistan
panamá
pattern-matching
pbandk
pdx
peru
philippines
phoenix
pinoy
pocketgitclient
polish
popkorn
portugal
practical-functional-programming
proguard
prozis-android-backup
pyhsikal
python
python-contributors
quasar
random
re
react
reaktive
realm
realworldkotlin
reductor
reduks
redux
redux-kotlin
refactoring-to-kotlin
reflect
refreshversions
reports
result
rethink
revolver
rhein-main
rocksdb
romania
room
rpi-pico
rsocket
russian
russian_feed
russian-kotlinasfirst
rx
rxjava
san-diego
science
scotland
scrcast
scrimage
script
scripting
seattle
serialization
server
sg-user-group
singapore
skia-wasm-interop-temp
skrape-it
slovak
snake
sofl-user-group
southafrica
spacemacs
spain
spanish
speaking
spek
spin
splitties
spotify-mobius
spring
spring-security
squarelibraries
stackoverflow
stacks
stayhungrystayfoolish
stdlib
stlouis
strife-discord-lib
strikt
students
stuttgart
sudan
swagger-gradle-codegen
swarm
sweden
swing
swiss-user-group
switzerland
talking-kotlin
tallinn
tampa
teamcity
tegal
tempe
tensorflow
terminal
test
testing
testtestest
texas
tgbotapi
thailand
tornadofx
touchlab-tools
training
tricity-kotlin-user-group
trójmiasto
truth
tunisia
turkey
turkiye
twitter-feed
uae
udacityindia
uk
ukrainian
uniflow
unkonf
uruguay
utah
uuid
vancouver
vankotlin
vertx
videos
vienna
vietnam
vim
vkug
vuejs
web-mpp
webassembly
webrtc
wimix_sentry
wwdc
zircon
Powered by
Title
d

dstarcev

10/22/2018, 9:20 AM
But it creates a new scope isn't it?
j

Jonathan

10/22/2018, 9:20 AM
suspend inline fun <T, R> Iterable<T>.mapAsync(
    crossinline transform: suspend (T) -> R
) = coroutineScope {
  map { async { transform(it) } }.map { it.await() }
}
Yes, and that what you want.
You want
mapAsync
to suspend until all jobs are completed
But you also want
mapAsync
to throw as soon as one job fail.
g

gildor

10/22/2018, 9:21 AM
You can use coroutineScope, but why not just use GlobalScope in this case?
j

Jonathan

10/22/2018, 9:21 AM
And you also want to make sure all job started are canceled in this case
With GlobalScope jobs are not cancelled in case of failure
Global scope just leaks the coroutines
d

dstarcev

10/22/2018, 9:22 AM
I am quite new to coroutines, is it correct for a function to have it's own scope ignoring whatever it is on the caller site?
g

gildor

10/22/2018, 9:23 AM
awaitAll does the trick for you and nothingg will leak
so it’s exactly the use case of awaitAll and documentation explicitly mentions how awaitAll is different from .map { it.await() }
j

Jonathan

10/22/2018, 9:24 AM
Yes true. However, I tend to find
coroutineScope
more explicit
g

gildor

10/22/2018, 9:24 AM
what can be more explicit than awaitAll?
this is exactly what must be used
and coroutineScope even not used in this case
and provides useless scope
is it correct for a function to have it’s own scope ignoring whatever it is on the caller site
No,
coroutineScope
uses
coroutineContext
of outer scope
d

dstarcev

10/22/2018, 9:27 AM
suspend inline fun <T, R> Iterable<T>.mapAsync1(
    crossinline transform: suspend (T) -> R
) = coroutineScope { map { async { transform(it) } }.awaitAll() }

suspend inline fun <T, R> Iterable<T>.mapAsync2(
    crossinline transform: suspend (T) -> R
) = map { GlobalScope.async { transform(it) } }.awaitAll()
j

Jonathan

10/22/2018, 9:27 AM
Both solutions are fine
I prefer the first one, but it is opinionated style.
In both cases no coroutine is leaked
g

gildor

10/22/2018, 9:28 AM
There is semantical difference between 2 solutions
d

dstarcev

10/22/2018, 9:28 AM
btw, what difference will it make if I specify the receiver?
suspend inline fun <T, R> Iterable<T>.mapAsync2(
    crossinline transform: suspend CoroutineScope.(T) -> R
) = map { GlobalScope.async { transform(it) } }.awaitAll()
g

gildor

10/22/2018, 9:28 AM
coroutineScope solution uses outer context
but GlobalScope uses DefaultDispatcher
j

Jonathan

10/22/2018, 9:29 AM
true
g

gildor

10/22/2018, 9:29 AM
also I would pass dispatcher for this function, so you could use this function for blocking IO
d

dstarcev

10/22/2018, 9:30 AM
in what way?
g

gildor

10/22/2018, 9:31 AM
because solution with GlobalScope in your current version uses Default dispatcher by default
so you shouldn’t use it for blocking code
for blocking code you should use IO explicitly
coroutineScope uses dispatcher of outer scope
so you can wrap it to
withContext(<http://Dispatchers.IO|Dispatchers.IO>)
This will not work for GlobalScope
d

dstarcev

10/22/2018, 9:35 AM
May I add this in the place where I create the initial scope?
runBlocking(<http://Dispatchers.IO|Dispatchers.IO>) {
...
}
the intention in my case is to parallelize blocking operations
g

gildor

10/22/2018, 9:54 AM
runBlocking IO doesn’t make any sense in this case
if you usr runBlocking with coroutineScope, you will have 1 (main) thread execute all your tasks
d

dstarcev

10/22/2018, 9:57 AM
In case I write a blocking server and sometimes want to parallelize tasks, what do I do?
g

gildor

10/22/2018, 9:58 AM
Use GlobalScope
+ dispatcher on your choice