This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-06-03
Channels
- # admin-announcements (2)
- # alda (4)
- # beginners (15)
- # boot (89)
- # cljs-dev (88)
- # cljsrn (75)
- # clojure (149)
- # clojure-belgium (16)
- # clojure-france (2)
- # clojure-greece (6)
- # clojure-russia (108)
- # clojure-spec (39)
- # clojure-taiwan (3)
- # clojure-uk (7)
- # clojurescript (70)
- # css (3)
- # cursive (17)
- # data-science (2)
- # datascript (7)
- # datomic (41)
- # dirac (3)
- # hoplon (12)
- # instaparse (1)
- # juxt (3)
- # lambdaisland (9)
- # mount (4)
- # off-topic (6)
- # om (71)
- # om-next (4)
- # onyx (22)
- # other-languages (56)
- # perun (15)
- # proton (6)
- # re-frame (32)
- # reagent (42)
- # specter (34)
- # spirituality-ethics (7)
- # tmp-json-parsing (5)
- # untangled (13)
- # vim (4)
- # yada (6)
@mccraigmccraig: I see, but that means catching each error in an operation on a stream. Or have you implemented alternative versions of s/map s/filter s/transform?
Streams feels a bit like pre-transducer core.async. It didn't have any error handlers either
the errors on deferreds is one of the most appealing features of manifold. It works so much nicer then core.async error handlers. But with streams, it feels like something's lacking on the error-handling front
@stijn in my case error processing is just part of my processing pipeline... a Streams based short-circuit for errors would be pretty nice though
@malcolmsparks: Hi Malcolm, have you had a chance to look at the file upload problem I mentioned a few days ago?