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
EventStream.delay(100, ev) should not evaluate ev until after 100ms have passed.
ev should be re-evaluated every time the stream starts, unless emitOnce = true is set (then subsequent starts don't emit anything, same as now)
This would make EventStream.delay(ms, ev) behave the same as EventStream.delay(ms).mapTo(ev) rather than EventStream(ev).delay(ms).
(Note: EventStream.apply is the future alias to EventStream.fromValue, not yet available)
I don't know, maybe we should even remove the ability to pass ev to EventStream.delay at all, to force users to clarify their intent. With the new apply alias, both options will become quite ergonomic to write.
The text was updated successfully, but these errors were encountered:
EventStream.delay(100, ev)
should not evaluateev
until after 100ms have passed.ev
should be re-evaluated every time the stream starts, unlessemitOnce = true
is set (then subsequent starts don't emit anything, same as now)This would make
EventStream.delay(ms, ev)
behave the same asEventStream.delay(ms).mapTo(ev)
rather thanEventStream(ev).delay(ms)
.(Note:
EventStream.apply
is the future alias toEventStream.fromValue
, not yet available)I don't know, maybe we should even remove the ability to pass
ev
toEventStream.delay
at all, to force users to clarify their intent. With the newapply
alias, both options will become quite ergonomic to write.The text was updated successfully, but these errors were encountered: