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

Daniele Segato

09/18/2020, 4:24 PM
How would you write a suspend function to share the result of a function between parallel requests? Let me explain with pseudo-code
private var shared: Deferred<Result>? = null

private suspend fun actuallyGrabResult(): Result { ... }

suspend fun grabResult(): Result {
  val deferred = shared.takeUnless( !shared.isActive }
    ?: async { actuallyGrabResult() }
        .also { shared = it }
  return deferred.await()
}
The idea is that only 1
actuallyGrabResult()
coroutine at a given time should be running and any request to
grabResult()
should wait for it and get the result. Until the result is delivered, next requests will cause another call. With RxJava you'd do something like:
private val shared: Single<Result> = actuallyGrabResult()
        .toObservable()
        .replay(1)
        .refCount()
        .singleOrError()

private fun actuallyGrabResult(): Single<Result> { ... }

fun grabResult(): Single<Result> {
  return shared
}
Is there an idiomatic way of doing this with coroutine? (I've only recently started using coroutines)
z

Zach Klippenstein (he/him) [MOD]

09/18/2020, 4:32 PM
See https://kotlinlang.org/docs/reference/coroutines/composing-suspending-functions.html#lazily-started-async
private val shared = scope.async(start = CoroutineStart.LAZY) { actuallyGrabResult() }

suspend fun grabResult(): Result = shared.await()
Where
scope
is a
CoroutineScope
owned by your class and tied to its lifetime. This works great if your class has its own lifetime (i.e. has some kind of
dispose()
method) and thus is its own logical “scope”. If your class doesn’t have its own lifetime, then it’s trickier because you probably need to do some kind of ref counting of the callers of
grabResult()
to correctly scope your internal coroutine(s), both for cancellation and error handling. This is what libraries like https://github.com/dropbox/Store help with, because that logic can get complicated.
s

streetsofboston

09/18/2020, 4:34 PM
Yup, calling
await()
on a
Deferred
will not restart the coroutine of the
async
that built it.
d

Daniele Segato

09/20/2020, 9:00 AM
yeah the problem with that is that it will only run the first time it is executed, while what i want is for it to run exactly 1 job at a given time, so if 3 request come while it is running they'll receive the same result (error or result) and after that if someone call it again it should launch the job/coroutine again
with RxJava was fairly easy to achieve (see example above)
s

streetsofboston

09/20/2020, 2:11 PM
Maybe something like this (didn't try the code snippet below out, but the idea is there), where
getResult()
is a suspend fun as well.
var sharedResult: Result? = null
val muted = Mutex()
...
suspend fun getSharedResult(): Result {
    sharedResult = null 
    return mutex.withLock {
        if (sharedResult != null) sharedResult
        else getResult().also { sharedResult =it }
    }
}
A call to
getSharedResult()
is made, causing
getResult()
to be called. If 3 new calls are coming before
getResult()
resumes/returns, the first caller to
getSharedResult()
will set
sharedResult
, which the following three return immediately. The 4th caller, who'll arrive way later, will set
sharedResult
to null again and
getResult()
is called for the 2nd time.
z

Zach Klippenstein (he/him) [MOD]

09/20/2020, 3:36 PM
Once shareIn comes out, I think you can do something similar to your rx solution with flows.
d

Daniele Segato

09/20/2020, 6:58 PM
Mutex Is interesting, is it Coroutines aware (the lock doesn't actually lock the thread)? I was thinking of a different way.
var shared: Deferred<Result> = buildAsync()

private fun buildAsync(): Deferred<Result> {
  return runBlocking {
    async(SupervisedJob, start = Lazy) {
       try {
          getResultInternal()
       } finally {
          shared = buildAsync()
       }
    }
  }
}

suspend fun getResult() : Result {
  return shared.await()
}
Would this work? I'll try tomorrow at work.
z

Zach Klippenstein (he/him) [MOD]

09/20/2020, 7:00 PM
The mutex from the coroutines library is coroutines aware 🙂
Your
buildAsync
isn’t async, since it uses
runBlocking
, it won’t return until
getResultInternal()
returns. And since
runBlocking
won’t return until all its child coroutines have finished, i think there’s no point in starting the
async
coroutine lazily, since
runBlocking
will immediately join on it and cause it to start. It also recurses infinitely though, since the coroutine won’t finish until the recursive call finishes, which won’t finish until the next call finishes, etc – there’s no base case. And this code isn’t thread safe, since access to
shared
isn’t guarded with a lock.
I don’t think there’s a way to do this imperatively in coroutines today without using either a lock of some kind or a lock-free, CAS-based approach.
d

Daniele Segato

09/20/2020, 10:12 PM
Right, silly me, I wrote this in my mobile phone. First thing i would do after noticing would be replacing that with someContext.async. Tomorrow I'll experiment a bit, using mutex too. And maybe have a look at Store to see how they did it.
From my tests this works as I want it to work:
private val scope = parentScope + SupervisorJob() + Dispatchers.Unconfined

private var shared: Deferred<Result> = buildDeferred()

override suspend fun getResult(): Result {
    return shared.await()
}

private fun buildDeferred(): Deferred<Result> {
    return scope.async(start = CoroutineStart.LAZY) {
        try {
            getResultInternal()
        } finally {
            shared = buildDeferred()
        }
    }
}

private suspend fun buildResultInternal(): Result {
    // network call or whatever
}
the only missing part is canceling the job if every
await()
is canceled but I think i can make it by adding a little bit of code + mutex on the
getResult()
function
I've also checked Dropbox Store 4, they do it differently but they need more stuff and they use Flow under the hood and channels.
@Zach Klippenstein (he/him) [MOD] @streetsofboston thanks by the way!
👍 1