I'm not too excited about the proposed syntax, because x.with(y) makes
it seem that x and y are not the same, it feels like an operation that
is performed on x. At least to me, something like
ObservableValue.tie(x, y).map((x, y) -> {...}) looks more intuitive.
But then the additional value on top of the existing
Bindings.create*Binding() may seem a bit marginal. On the other hand,
the null-eliding behavior may improve ergonomics a lot for some
people.
- JEP Proposal: Fluent Bindings for multiple observables John Hendrikx
- Re: JEP Proposal: Fluent Bindings for multiple observ... Nir Lisker
- Re: JEP Proposal: Fluent Bindings for multiple ob... John Hendrikx
- Re: JEP Proposal: Fluent Bindings for multipl... Nir Lisker
- Re: JEP Proposal: Fluent Bindings for mul... John Hendrikx
- Re: JEP Proposal: Fluent Bindings for multiple observ... Andy Goryachev
- Re: JEP Proposal: Fluent Bindings for multiple ob... John Hendrikx
- Re: JEP Proposal: Fluent Bindings for multiple observ... Michael Strauß
