Yeah, it looks like the Binding is being bound to the stack trace

Right?

yup

This might make more sense.

...

@User uploaded a file: Untitled

yes

I don't know if that can be fixed for Java

someObservable.toBinding(e -> e.printStackTrace())

But it doesn't look as bad as Kotlin

I dont like the java version either 😉

its sends a confusing message

Let me think about what to do with Java one. It is following the

Subscriber

convention, as in

subscribe(t -> System.out.println(t), e -> e.printStackTrace())

. But the semantics of

toBinding()

are confusing , you are right.

the connectableObservable part

the kotlin should that be

@User uploaded a file: Untitled

I would have expected

toConnectableObservable()

That part I do not own : ) Netflix and Dave Akarnokd gave it that name

I think that would have been a better name though

yeah but in the java part it is a

ConnectableObservable<boolean>

in kotlin there does not seem to be a difference between

toObservable

and

toConnectableObservable

I think I follow... it returns a

ConnectableObservable

for both. Kotlin just inferred the type.

its not clear API wise

and its not clear from the text

Okay let me see if I can clarify that. I don't know if I can do anything about the API because that is the RxJava/RxKotlin domain...

If there is a better function name it can be filed as an issue for RxKotlin project at least.

well I read it

chapter 6 is IMO too long

maybe split it up

I thought I was cramming a bit, especially since I wanted to be thorough. Moving Dialogs and Multicasting into a separate chapter should cut it in half. Thanks @ron!

np

@ron I filed an issue