kotlinx.coroutines version 0.26.0 is released with Structured Concurrency and it is such a major change that there is a separate post explaining it:https://medium.com/@elizarov/structured-concurrency-722d765aa952 …
-
What if I need multiple Scopes? Like `lifecycleOwner`(or `this`) and `viewLifecycleOwner` on Fragments?
By defining a coroutineScope on Lifecycle, you can use it on any one, including Fragment's viewLifecycle:https://gist.github.com/LouisCAD/58d3017eedb60ce00721cb32a461980f#file-lifecyclejob-kt-L30 …
-
-
Why not createJob().also {}
-
Because I need to return the created coroutine scope (which includes the created job)
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.