This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-04-11
Channels
- # aleph (1)
- # architecture (18)
- # beginners (57)
- # boot (13)
- # cider (47)
- # cljs-dev (28)
- # cljsjs (13)
- # cljsrn (39)
- # clojure (258)
- # clojure-greece (16)
- # clojure-italy (2)
- # clojure-miami (1)
- # clojure-nl (9)
- # clojure-poland (15)
- # clojure-russia (369)
- # clojure-spec (53)
- # clojure-uk (49)
- # clojureremote (3)
- # clojurescript (135)
- # core-matrix (1)
- # cursive (11)
- # datascript (3)
- # datomic (4)
- # emacs (12)
- # figwheel (13)
- # hoplon (7)
- # interop (7)
- # jobs-discuss (33)
- # lumo (28)
- # off-topic (15)
- # om (7)
- # onyx (26)
- # pedestal (10)
- # perun (1)
- # planck (10)
- # re-frame (54)
- # reagent (16)
- # ring (5)
- # ring-swagger (50)
- # rum (2)
- # spacemacs (2)
- # unrepl (125)
- # untangled (12)
@jfntn can you give some context? What's the benefit of using transducers on ratoms?
@pesterhazy was just trying to see if it'd work'
what about making an async transduction on an iterator based on add-watch?
does anyone know or have any experience with any good libraries for creating editable flowcharts using reagent?
Preferably it’d be reagent oriented, but a React lib could do too. I was wanting to target <svg>, but I’m guessing that’d be the most likely candidate for a React based lib anyways.
@noisesmith not sure I understand what the benefits would be?
probably not useful in this case, but I can see cases where I’ve used add-watch in non-reagent code that would have been more convenient as a transducer across modifications
The snippet above seems to work, but I don’t think this will play well with stateful transducers, it never calls the 1-arity of the rf so for some kinds of transducers that do aggregation it probably would never return a value
Not sure if there’s a good solution to interop, since the semantics are pretty different
right- but those aren’t valid for anything of indeterminate lifetime anyway
Right they’d produce a value when the coll is finished processing, which would never happen for a ratom, unless :on-dispose
passes a final value down? I’ve never used that
I could see it working if you had an intermediate object to transduce on, with a disconnect method - then it’s up to your code to decide when wrapping up the stateful transducers and finalizing a result is apropriate
perhaps taking the reaction or watch and deriving an iterator from that, and the transducing on the iterator, closing the iterator if/when apropriate