Isn’t it better to approach async from coroutines point of view for Kotlin?

orangy: Yeah that might be a good go-to since it is native to Kotlin.

Suspension is a natural point where traveling across nodes can occur transparently, but that would need serialization of coroutine state, I suppose. @elizarov ?

agreed, especially since the stackless limitation was dropped, it seems like the go-to solution. a lot less complicated than quasar's post instrumentation

@thomasnield Take a look at this guide. It explicitly addresses coroutines-Rx interop: https://github.com/Kotlin/kotlinx.coroutines/blob/master/reactive/coroutines-guide-reactive.md

@elizarov bookmarked, thank you. I probably should include this in my upcoming Packt book on RxJava, in the chapter covering Kotlin interop.