How can I cancel something using another scope? I have a class that has it's own lifecycle scope. N...

# coroutines

[Paul Woitaschek]

How can I cancel something using another scope?

I have a class that has it's own lifecycle scope. Now when someone calls a suspend funtion on that class I want that function to get cancelled when the scope of the class is cancelled.

[tseisel]

Try with withContext(myClassScope.coroutineContext) . I'm not sure it is good practice, but this seems to have the behavior you want.

[streetsofboston]

I wrote a blurb about how to manage lifecycles and CoroutineScopes, including the situation you describe (one object with one lifecycle calling another object with a different lifecycle):

“How can we use CoroutineScopes in Kotlin?” by Anton Spaans https://link.medium.com/duBgcEy6J1

[Paul Woitaschek]

But isn't what you describe the other way round? I need to cancel it when the first of the two scopes gets cancelled

[streetsofboston]

I think you'll find that at the end of my article:

... Let’s flip it around. What happens if that other CoroutineScope finishes, gets canceled? What would happen to the calling CoroutineScope? ...

...

... the calling Coroutine will be canceled, but the CoroutineScope in which it runs remains active ...

[Paul Woitaschek]

Ah right

[Paul Woitaschek]

Actually kotlin complains and suggests to replace your async - await with exactly what @tseisel wrote

[Paul Woitaschek]

Ooh and it seems that the inspection is wrong

[streetsofboston]

When you do scope.async { … }.await() or just where the scope is the same one as the calling scope or do async { … }.await(), using withContext makes sense and the linter suggests that.
Using withContext to change scope seems wrong to me…. it probably works, but for some reason, it ‘looks’ wrong…

[Paul Woitaschek]

Nope it doesnt work for some reason, the inspection is wrong

[Paul Woitaschek]

https://gist.github.com/PaulWoitaschek/ad60a1deecea12cce8ff4475c2372583

[Paul Woitaschek]

The inspetion says we should replace the async-await so it looks like in the secon file.
But it's a completely different behavior

[Paul Woitaschek]

@elizarov Do you know this is already reported?

[streetsofboston]

Exactly…

[streetsofboston]

I think a CoroutineScope is more than just its coroutineContext (even though that is its only interface val).

[Paul Woitaschek]

Well the test shows that it certainly is more than the context

[tseisel]

Some reminders on CoroutineContext VS CoroutineScope from Roman's blog post : https://medium.com/@elizarov/coroutine-context-and-scope-c8b255d59055