I don't see any opinions, so should I investigate option 2?
- Nir
On Thu, Mar 29, 2018 at 4:36 AM, Kevin Rushforth wrote:
> Breaking existing apps is the one thing I worried about with the
> suggestion of doing it without API changes. So to summarize I think there
> are three possiblities:
>
>
Breaking existing apps is the one thing I worried about with the
suggestion of doing it without API changes. So to summarize I think
there are three possiblities:
1. Just make the current API lazy for observables with no resource for
the developer. This seems unwise for the reasons you point o
Iv'e given the idea of using existing API some thought.
When using primitives, the evaluation is always eager. A method that
returns a boolean (for example) will always be evaluated before it is
passed to When, regardless of the condition value. This precludes the
possibility of lazy evaluation in
Conceptually what you describe sounds like a good approach to explore.
Another approach worth exploring is to see whether this can be done
without API change, using the existing API. I took a (very quick) look
and didn't see anything that would preclude fixing this using the
existing API, nor
Hello,
I've proposed to work on a public API for binding.When that adds
capabilities for dynamic evaluation of the 'then' and 'otherwise'
arguments. Any comments?
https://bugs.openjdk.java.net/browse/JDK-8199560
- Nir
