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
k

kd

01/29/2019, 7:15 PM
In a non lifecycle class, how should we use coroutines? I have read that your class should extend CoroutineScope if it is a lifecycle class (Activity, fragment, viewmodel). But in just a simple business logic class, how would you use CoroutineScope?
a

Allan Wang

01/29/2019, 7:15 PM
If there's truly no lifecycle, then maybe something like global scope
however, in reality, anything you do that is tied to the UI will have a lifecycle. If you are running things in a service, the service itself also has a lifecycle
k

kd

01/29/2019, 7:17 PM
Good point that everything is eventually tied to a lifecycle, so we should pass the coroutine scope as a dependency to the non lifecycle classes?
a

Allan Wang

01/29/2019, 7:19 PM
There are a few ways of doing things. You can create functions that extend CoroutineScope so the caller supplies their own scope. You can also write suspension functions that either checks for cancellation or is wrapped by a cancellable coroutine. Coroutines need to cooperate to be cancelled, but for the most part you don't really have to worry about explicitly cancelling it within the code
For me personally, I use a lot of suspension functions, and I declare the context from which it runs (IO vs UI). Switching contexts will already halt if the scope is cancelled. Otherwise, you can use
yield()
, which allows other coroutines to run and will cancel if the job is cancelled
g

ghedeon

01/29/2019, 7:21 PM
yeah.. seems like the official suggestion is to proxy your
CoroutineScope
all the way down, from UI to Data... The code starts looking really strange tho.. If you're lucky to have only
coroutineScope{}
use cases than its cleaner and
suspend
is enough.
k

kd

01/29/2019, 7:21 PM
Great, thanks for the comments guys!
g

gildor

01/30/2019, 1:31 AM
You need to pass scope only if you run some background tasks, otherwise suspend and coroutineScope as @ghedeon mentioned. Also, not sure why API will look strange, this is usual thing without coroutines. If you don’t want leak background job you have to manage lifecycle somehow
✔️ 2
d

Davide Giuseppe Farella

01/30/2019, 7:19 AM
Basically: * I wanna wait for this function to complete and, eventually, get a result
suspend fun doJob() {  }
* same as above, but I need that function to do some works asynchronously
suspend fun doJob() = coroutineScope {  }
* I wanna launch something and don't wait for it to complete
fun CoroutineScope.doJob() = launch {  }
g

gildor

01/30/2019, 7:21 AM
yes, or just:
fun doJob(scope: CoroutineScope) = scope.launch {  }
But launch probably is a bad example, I don’t see use cases for launch. Only valid case what I see it’s
actor{}
or
produce{}
1
d

Davide Giuseppe Farella

01/30/2019, 7:23 AM
I didn't need that yet, yesterday I dealt with it for the first time and
launch
seems to fit my use case, I'll take a look at those apis 🍻
g

gildor

01/30/2019, 7:23 AM
nono
I don’t think that you shoul use actor or produce isntead of launch
I just talking about your example:
fun CoroutineScope.doJob() = launch {  }
d

Davide Giuseppe Farella

01/30/2019, 7:24 AM
Yep, me too 😋
g

gildor

01/30/2019, 7:25 AM
instead of launch, just use common suspend function to do job, and if client code want to launch it as task, just wrap it to launch inside your scope
d

Davide Giuseppe Farella

01/30/2019, 7:26 AM
operator fun CoroutineScope.invoke(
            channels: SendChannel<IChannel>,
            groups: SendChannel<ChannelGroup>,
            errors: SendChannel<ChannelError>
    ) = launch { /* do smtng and deliver to Channels */ }
That's my use case, I used
launch
since I don't want to wait for this function tu complete, once is called
g

gildor

01/30/2019, 7:29 AM
But why?
I see what you mean. Channels ccase
Yes, this is valid case. also you can use
produce{}
for this
✔️ 1
But this API looks a bit strange for me
d

Davide Giuseppe Farella

01/30/2019, 7:37 AM
Which one? You mean
produce
or my function?
g

gildor

01/30/2019, 7:37 AM
invoke for coroutine scope
d

Davide Giuseppe Farella

01/30/2019, 7:40 AM
Oh ok. That's just a parser class, that makes sense to have only a function that is invoke, since the class purpose it's already clear 😁. What is weird for me is the way to call the api
parser.run { this@scope( /* channels */ ) }
. Still working on it 😁
It would be great to have
launch { parser( /* channels */ ) }
anyway I'm goin off topic 😋 I already posted that question on #general and ghideon told me that already thousands of people made the same question 😁
g

gildor

01/30/2019, 7:44 AM
I believe this highly depends on use case
👍 1
It would be great to have
launch { parser( /* channels */ ) }
But you can have such API
k

kd

01/30/2019, 3:10 PM
@gildor and Davide, thanks for the discussions. They help a lot. Coming to unit testing coroutines. How would you test fun CoroutineScope.doJob() = launch { } Runblocking?
d

Davide Giuseppe Farella

01/30/2019, 3:19 PM
I successfully tested with
runBlocking
, AFAIK it's the best ( only? ) way
k

kd

01/30/2019, 3:27 PM
Yup, was just curious if there is any other way. One thing I have been recommended is to separate the launch and the actual code inside launch to a suspend method and just test the suspend method using runBlocking
g

gildor

01/30/2019, 4:34 PM
runBlocking will work, but because launch doesn't return any result you have to check side effect, test suspend function is way easier, it's the same as testing side effect and pure functions
And again, in your place I would just consider do you really need launch (so some background job that does side effect only) or you can replace it with suspend function
✔️ 2