> and having nullable types would be nice too. ...

# rx

[antonrutkevich]

and having nullable types would be nice too.

That’s indeed the biggest pain with RxJava in Kotlin ) And, yes, I don’t see how that can be solved without either wrapping the Observable with the new base reactive type (null-aware, as it’s Kotlin) or rewriting RxJava in Kotlin.

I’m not sure the latter would be a good solution, as RxJava has lots of complex logic in it, so rewriting it all in Kotlin just to get null-aware streams sounds like an overkill.