This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-03-16
Channels
- # autochrome-github (17)
- # aws (6)
- # babashka (19)
- # beginners (42)
- # bristol-clojurians (1)
- # calva (1)
- # cider (7)
- # clara (1)
- # clj-kondo (6)
- # cljdoc (17)
- # cljs-dev (5)
- # clojars (23)
- # clojure (93)
- # clojure-europe (20)
- # clojure-italy (28)
- # clojure-nl (13)
- # clojure-sanfrancisco (1)
- # clojure-uk (50)
- # clojuredesign-podcast (5)
- # clojurescript (90)
- # core-async (8)
- # datomic (23)
- # duct (3)
- # emacs (10)
- # figwheel-main (1)
- # fulcro (1)
- # malli (1)
- # meander (22)
- # off-topic (12)
- # pathom (57)
- # reitit (4)
- # remote-jobs (5)
- # shadow-cljs (5)
- # sql (8)
- # tools-deps (3)
is there a decent way to differenciate a promise-chan from another type of chan? I think I can just tap into internals (look at channel.buf) but I am not sure that's something I'd like to do
I am in a case where I can optimize the consumer side depending if it's a single value or N
As I understand it, you pass a promise-chan only when the consumer already expects to consume just once. May I ask what’s your case in more detail?
no not really. Think setting up http content-length early (upon sending headers) for single shot response vs chunked header for N messages). I could set chunked for all and be done with it. but it is problematic to do that for a few reasons and I'd rather avoid it.