Fork me on GitHub
#specter
<
2016-12-09
>
mpenet08:12:02

is there a (recommended) way to compose transforms ? I mean other than just (->> x (transform ...) (transform ...)) etc

mpenet08:12:06

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)

mpenet08:12:22

Oh I see multi-transform and compiled-multi-transform could be it

bfabry08:12:30

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 😉

bfabry08:12:15

but I don't see anything atm

mpenet08:12:42

yeah, hard to map to transducers maybe. I was more thinking of some kind of navigation/transformation planner depending on some composition of both

mpenet08:12:43

but yeah, not an easy task

nathanmarz12:12:58

@mpenet yea you want to use multi-transform

bfabry18:12:42

are there performance benefits to using multi-transform over intermediate collections?

nathanmarz18:12:10

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

mpenet19:12:32

That s what I ended up using, thanks ;)