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
The following code returns Loading on the second value access, unless we bind (and thus wake up and do the triggerAsync thing). Only happens on the v1 branch, master is fine:
I'm not 100% sure that I like it, but the basic idea is that if the async computation is expensive, then it gets suspended if nobody is interested.
In the above example, nobody is observing any changes. You happen to know that if you wait long enough, the computation should have finished, but that is not quite the rule.
That being said, I'm not very thrilled with the new behavior myself. But I'd be eager to learn more about things that approximate real world use cases, in the hopes of coming up with something that has the intended benefits of #60, without messing up expectations.
The following code returns
Loading
on the second value access, unless we bind (and thus wake up and do the triggerAsync thing). Only happens on thev1
branch,master
is fine:The text was updated successfully, but these errors were encountered: