Yes < robin> you can do it this way ``` coroutineScope val d kotlinlang #coroutines

coroutineScope {
    val daemonLikeJob = launch { while (true) /* Do sth until everything is done */ }
    coroutineScope {
        launch { /* do work */ }
        launch { /* do work */ }
    }
    daemonLikeJob.cancel()
}

robin

10/22/2018, 12:44 PM

That requires me to define the deamon job first, which doesn't feel good to me - what if I want to start the daemon job from inside a function that doesn't know about the rest of the coroutine scope?

Ideally I'd like a function

launchDaemon

or a way to tell launch via its

context

parameter that I want daemon-like behavior, without having to know any of the surrounding code and the current coroutine scope. I'd write that function myself but not sure how right now.

louiscad

10/22/2018, 1:03 PM

Don't you think it's risky to do it the other way around?

robin

10/22/2018, 2:30 PM

Not sure why that would be risky. Can you explain why you think so?

louiscad

10/22/2018, 2:43 PM

You may not know a function will launch a coroutine that has a larger scope. But I think that greatly depends on the implementation though

robin

10/22/2018, 3:10 PM

It won't be a larger scope, though, that's the whole point. It should get cancelled when the containing scope wants to finish.

louiscad

10/22/2018, 3:14 PM

I think you can get the job from the context (

val scopeJob = coroutineContext[Job]!!

), launch the daemon from

GlobalScope

or another global but custom scope, and call

scopeJob.invokeOnCompletion { daemonJob.cancel() }

robin

10/22/2018, 3:16 PM

That should work, thanks! Still feel it's a little hacky, but if there's no official support for this it's probably as good as I can do.

2 Views

#coroutines Join Slack