Expose view properties as subjects?

[jakewharton]

Expose view properties as subjects?

[dlew]

Would this mean that calling compoundButtonSubject.onNext(true) would cause the compound button to become checked?

If that's the case, then I am getting a nervous feeling about this because it's moving away from a functional approach and instead depends on side effects. With the two separated there is clearly a cause and an effect, with it combined then the effect could be a cause.

[JakeWharton]

Maybe we'll just do this internally with a dedicated type.

I don't necessarily want a side-effect-having Subject but rather want a single type with which I can both observe values and update values. This is especially desired in situations where I want to have a single type that I can inject to hide the underlying mechanism (views aren't a good example in this case. think: preferences).

I'm envisioning a simple Property<T> extends Observable<T> implements Action1<T> or a Property<T> which is a factory for Observable<T>s and Action1<T>s.