SE-0475: Transactional Observation of Values

[hassila (Joakim Hassila)]

@gwendal.roue

At this point, the app is displaying the obsolete initial value, and will never display anything else until the name is modified again. This goes against most expectations, will thus trigger bug reports, and that's why I call this a bug.

This is actually very reminiscent of the similar issue we encountered in throttled sequences:

Surprising semantics of throttled sequences

After some experimenting today after seeing unexpected behavior I just realized that the throttled async stream behaves in a quite unexpected manner. Basically the current semantics easily leads to lost Updates/wakeups. AFAICT the current semantics are that if a new event comes in within the specified throttled time on the base async sequence, it’s not forwarded. But after the specified throttled time has elapsed- it’s not forwarded either until a new event comes from the base sequence. So ba…

(which is still an issue AFAIK, we stopped using them (unfortunately, would like to!) after that one)