You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Without any investigation of any kind, I remember some strange Scala behavior back from the 2.x times (where x < 10), that resulted in the compiler (?) executing a closure prematurely at definition time to get the actual return type. This is some dark memory, and I may totally reproduce it wrong, but I wanted to mention it at least once. If I find any reference to that issue, I will add it later...
Fixes#2946
In `evaluateNamed`, after evaluating `Task`s we are matching for
`ImputImpl[_]` instances to construct a `Watchable`.
A `Watchable` instance contains a `hashCode` for the current result and
a callback to evaluate it again and get the next result.
Instead of using the current result which was contained in `TaskResult`,
we were already calling the `recalc` callback, which executes again the
`T.input`s and performs their side effects twice.
Now we are returning the hashCode for the already computed result, so we
don't execute the `recalc` callback right away.
Pull Request: #2952
Reproduction
Current behavior
Expected behavior
It should print
bla
once:The text was updated successfully, but these errors were encountered: