This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-05-18
Channels
- # ai (1)
- # beginners (71)
- # boot (15)
- # cider (26)
- # clara (4)
- # cljs-dev (81)
- # cljsrn (26)
- # clojure (393)
- # clojure-berlin (2)
- # clojure-dev (5)
- # clojure-dusseldorf (1)
- # clojure-greece (5)
- # clojure-italy (6)
- # clojure-russia (97)
- # clojure-serbia (11)
- # clojure-sg (2)
- # clojure-spec (14)
- # clojure-uk (66)
- # clojurescript (58)
- # core-async (19)
- # cursive (18)
- # data-science (2)
- # datomic (75)
- # emacs (20)
- # events (5)
- # figwheel (1)
- # graphql (2)
- # hoplon (29)
- # jobs-discuss (3)
- # juxt (6)
- # lein-figwheel (1)
- # london-clojurians (2)
- # lumo (29)
- # mount (9)
- # off-topic (4)
- # om (16)
- # onyx (25)
- # other-languages (2)
- # pedestal (38)
- # protorepl (2)
- # re-frame (20)
- # reagent (9)
- # ring-swagger (6)
- # sql (10)
- # unrepl (3)
- # untangled (19)
- # utah-clojurians (1)
- # videos (2)
- # vim (20)
so, let’s say i want to enforce a ‘final’ action on a channel (e.g. sending the results to a destination HTTP endpoint), what would be the most idiomatic approach to do this ? my gut tells me this should probably be a reduce operation, but i’m not sure what other approaches are possible
the advantage of the reduce
approach is that it also automatically closes if there is no input left, and it feels the most “functional” approach
@lmergen I read this the other day, and I like how they are terminating their pipeline https://tech.grammarly.com/blog/building-etl-pipelines-with-clojure
not on a channel, on a pipeline, and pipeline might do the right thing there, I froget
the reason the outputting to a closed channel thing makes me sad is they have built this parallel processing pipeline with no way to tell when it is done
I dunno, on the one hand you want people to be happy with their choice of using clojure, on the other hand what they have shared is flawed in many ways
All work and no play makes Jack a dull boy