I wouldn’t make any claims about “best practices” but I’ve been playing with transducers in my little project:
https://github.com/miner/transmuters I have a blog post about how to “chain” transducers. (Not sure that’s the best term.) Basically, I wanted to use a transducer that might terminate (as with ‘take’), and then have another transducer pick up the input from there. The “chain” transducer is like a sequential combination of transducers. Of course, you can mix ‘chain’ and ‘comp’ to make work flows. http://conjobble.velisco.com/blog_posts/transducer-chain In any case, it was a fun experiment for me. Steve Miner stevemi...@gmail.com > On May 6, 2015, at 11:15 AM, larry google groups <lawrencecloj...@gmail.com> > wrote: > > I would like to write a detailed blog post about how developers are actually > using transducers. If you have a public project on Github that is using > transducers, would you please point me to it? I would like to see what you > did. > > If you are not using transducers, but you plan to in the near future, I would > be curious to see the code where you think they could help you. -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
