A modern programming language that makes developers happier.

kotlinlang

bit of a weird question.. is there anything like persisting a coroutine? like, its current state? and restoring it, to continue were it was before? or anything that points in this direction? could that even make any sense?

a bit weird, right? just an experimental thought in some android project.. context is backgrounding the app during some more involved flow.. and restoring it.. without having to do this on a - idk view model or something - level.. and instead just saying "resume the coroutines"..

low priority.. but any thoughts on this appreciated.. :blush:

<https://github.com/Kotlin/kotlinx.coroutines/issues/76>

If intermediate work can be persisted, it might be best to design it to resume where it left off, and that is also safe for app updates and code changes implied.