Closed lgrapenthin closed 3 years ago
Could you provide the implementation of run-task
as well ?
Its just #(% (partial println "success") (partial println "error"))
On 12/7/20, Léo NOEL notifications@github.com wrote:
Could you provide the implementation of
run-task
as well ?-- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: https://github.com/leonoel/missionary/issues/21#issuecomment-739829303
1 and 4 are certainly bugs, I'll investigate that.
2 is intended behavior. signal!
propagates lazy sampling semantics to its subscribers, so a signal!
with no subscriber won't consume anything at all. Assuming my-interval
represents the discrete stream of successive states of an identity, you can turn it into a continuous behavior using (relieve {} my-interval)
, effectively disabling backpressure upstream and exposing only the latest value downstream.
While playing around with reactor I stumbled across a couple bugs (on CLJS)
1
Expected: "pr2 1" is printed only once.
2
Printout
Expected: signal i2 wouldn't backpressure. N. b. core.asyncs mult doesn't backpressure when there are no takers - but independently I would expect i2 only to backpressure
my-interval
if it was am/stream!
3
4