This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-06-06
Channels
- # aleph (15)
- # beginners (40)
- # boot (14)
- # cider (90)
- # cljs-dev (132)
- # cljsrn (25)
- # clojars (7)
- # clojure (188)
- # clojure-chicago (4)
- # clojure-dusseldorf (1)
- # clojure-greece (9)
- # clojure-italy (43)
- # clojure-russia (16)
- # clojure-sg (7)
- # clojure-spec (39)
- # clojure-uk (81)
- # clojurescript (170)
- # component (5)
- # core-async (7)
- # cursive (49)
- # data-science (65)
- # datascript (3)
- # datomic (27)
- # graphql (3)
- # hoplon (4)
- # instaparse (56)
- # klipse (129)
- # leiningen (1)
- # lumo (28)
- # off-topic (4)
- # om (15)
- # onyx (54)
- # overtone (7)
- # pedestal (7)
- # re-frame (9)
- # reagent (72)
- # ring (33)
- # ring-swagger (2)
- # spacemacs (1)
- # untangled (19)
- # vim (2)
- # yada (12)
I have a list of files that I need to run a validation procedure that in most cases takes a few seconds, but might take upto 15 in rare cases, and I would like to run this validation in parallel on two files at a time, and then do further processing based on the result
am I right in assuming that pipeline-blocking
ran with a parallelism count of 2 would need to always wait for both validation procedures to finish before proceding to accept more values, because it maintains order?
yeah, if you don’t care about order just put some promise-chans in a set, use alts! and remove them as they complete
maybe there’s something simpler? but that should be pretty straightforward
actually - you don’t even need promise-chans, just make a set of async/thread calls, each one returns a chan