News for hackers. Stuff that matters.
Re:Anatomy of a Reducer by pron on Tuesday May 15, 2012 @02:06PM (#3977867)
If I understand correctly, does this mean that a map operation (that is not reduced further; i.e. we want a collection as the output) could be carried out in parallel efficiently using reducers only if there is an efficient (O(1)) way to concatenate the collections produced at each combining step (in the "internal nodes" of the fork-join computation tree)?

This would constrain how collections are implemented to make good use of this technique.

Re:Anatomy of a Reducer by weavejester on Tuesday May 15, 2012 @03:01PM (#3978191)
As I understand it, all of Clojure's internal data structures (save for the list, which can be substituted by a lazy seq) can be combined efficiently already.
Re:Anatomy of a Reducer by pron on Tuesday May 15, 2012 @03:08PM (#3978227)
True. I'm just wondering if this is indeed a requirement.