promisespromises.stream.promesa-csp — com.github.yapsterapp/promisespromises 3.0.361-alpha1

default-connect-via-opts clj/s

promesa-csp-buffer clj/s

(promesa-csp-buffer ch n)

promesa-csp-close! clj/s

(promesa-csp-close! ch)

promesa-csp-connect-via clj/s

(promesa-csp-connect-via src callback dst)

(promesa-csp-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

promesa-csp-error! clj/s

(promesa-csp-error! sink err)

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

promesa-csp-put! clj/s

(promesa-csp-put! sink val)

(promesa-csp-put! sink val timeout timeout-val)

promesa-csp-stream clj/s≠

clj

(promesa-csp-stream)

(promesa-csp-stream buffer)

(promesa-csp-stream buffer xform)

(promesa-csp-stream buffer xform _executor)

cljs

(promesa-csp-stream)

(promesa-csp-stream buffer)

(promesa-csp-stream buffer xform)

promesa-csp-take! clj/s

(promesa-csp-take! source)

(promesa-csp-take! source default-val)

(promesa-csp-take! source default-val timeout timeout-val)

promesa-csp-wrap-value clj/s

(promesa-csp-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 promesa-csp-take! because auto-unwrapping causes Promise<nil> from the stream to be indistinguishable from a closed channel - so wrapping promises sidesteps this

stream-factory clj/s