This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-12-09
Channels
- # adventofcode (187)
- # aws (1)
- # aws-lambda (1)
- # beginners (162)
- # boot (64)
- # cljs-dev (6)
- # cljsjs (2)
- # cljsrn (32)
- # clojure (357)
- # clojure-greece (1)
- # clojure-korea (4)
- # clojure-russia (63)
- # clojure-sanfrancisco (3)
- # clojure-spec (91)
- # clojure-uk (63)
- # clojurescript (74)
- # clojurex (10)
- # code-reviews (55)
- # core-async (4)
- # core-typed (1)
- # cursive (17)
- # datascript (36)
- # datomic (43)
- # devcards (4)
- # dirac (3)
- # emacs (59)
- # hoplon (286)
- # jobs-discuss (399)
- # luminus (4)
- # mount (9)
- # off-topic (30)
- # onyx (53)
- # protorepl (3)
- # re-frame (88)
- # reagent (4)
- # spacemacs (1)
- # specter (14)
- # untangled (1)
- # vim (42)
is there a (recommended) way to compose transforms ? I mean other than just (->> x (transform ...) (transform ...)) etc
I suspect there might be something to do that to allow a single pass over data applying all transforms in a smart way (or not)
I reckon the dot point at the bottom of the readme under "Future work" "any connection to transducers?" might be the final end game there 😉
yeah, hard to map to transducers maybe. I was more thinking of some kind of navigation/transformation planner depending on some composition of both
@mpenet yea you want to use multi-transform
are there performance benefits to using multi-transform over intermediate collections?
if you want to do two transforms in a row and they share part of the path, it will be more performant to do it as a multi-transform
there's some benchmarks for that: https://github.com/nathanmarz/specter/blob/master/scripts/benchmarks.clj#L307