Optimize Discrete data type by calming simultaneous events about reactive-banana HOT 6 CLOSED

Just to clarify, you are saying here that your intent is not merely to optimize Discrete while keeping its current semantics, but rather to change its semantics in a significant (though honestly, probably better) way as part of the process of optimizing it, right?

from reactive-banana.

By-the-way, the more I have been thinking about the possible consequences of simultaneous events in my own event networks, the more that calm seems like it would be a very helpful combinator. :-)

from reactive-banana.

Just to clarify, you are saying here that your intent is not merely to optimize Discrete while keeping its current semantics, but rather to change its semantics in a significant (though honestly, probably better) way as part of the process of optimizing it, right?

Well, I foreshadowed the intended semantics in the documentation: "Simultaneous events may be pruned for efficiency reasons." But yes, the changes event will only contain the latest update in the next version. This is what you would expect from a Behavior, anyway.

from reactive-banana.

That's fine, I was just making sure I understood this properly because it is a very significant change, as at the moment I have to code very cautiously using Discretes or in some cases avoid them altogether precisely because events are fired with "intermediate" results, and after your change I would not have to worry about this anymore. :-)

from reactive-banana.

Done! Commit 78bd983 in the development branch now contains the desired functions collect and spill.

from reactive-banana.

There, now it's done. The Discrete type will probably be merged into the Behavior type as issue #22 suggests, but it can't hurt to do it anyway.

from reactive-banana.