promisespromises.stream.core-async — com.github.yapsterapp/promisespromises 3.0.360-alpha1

async-buffer cljs

(async-buffer ch n)

async-close! cljs

(async-close! ch)

async-connect-via cljs

(async-connect-via src callback dst)

(async-connect-via src
                   callback
                   dst
                   {close-src? :promisespromises.stream/upstream?
                    close-sink? :promisespromises.stream/downstream?
                    :as _opts})

feed all messages from src into callback on the understanding that they will eventually propagate into dst

the return value of callback should be a promise yielding either true or false. when false the downstream sink is assumed to be closed and the connection is severed

async-error! cljs

(async-error! sink err)

this is also implemented in impl.. but circular deps...

async-put! cljs

(async-put! sink val)

(async-put! sink val timeout timeout-val)

async-stream cljs

(async-stream)

(async-stream buffer)

(async-stream buffer xform)

async-take! cljs

(async-take! source)

(async-take! source default-val)

(async-take! source default-val timeout timeout-val)

async-wrap-value cljs

(async-wrap-value v)

nils can't be put directly on core.async chans, so to present a very similar API on both clj+cljs we wrap nils for core.async

promises can be put on a core.async chan, but cause problems with async-take! because auto-unwrapping causes Promise<nil> from the stream to be indistinguishable from a closed channel - so wrapping promises sidesteps this

default-connect-via-opts cljs

stream-factory cljs