Re: CollReduce and IKVReduce for nil?

2013-01-25 Thread Andy Fingerhut
CLJ-1098 fix committed to Clojure master today as part of 1.5.0-RC3: http://build.clojure.org/job/clojure/changes Andy On Jan 14, 2013, at 4:24 AM, Wolodja Wentland wrote: On Sat, Jan 12, 2013 at 08:15 -0800, Andy Fingerhut wrote: The CLJ-1098 ticket was categorized as a minor

Re: CollReduce and IKVReduce for nil?

2013-01-14 Thread Wolodja Wentland
On Sat, Jan 12, 2013 at 08:15 -0800, Andy Fingerhut wrote: The CLJ-1098 ticket was categorized as a minor enhancement when it was created. Defects (i.e. bugs) are considered with higher priority. I can see that this categorisation caused this bug to be prioritised lower than actual bugs that

Re: CollReduce and IKVReduce for nil?

2013-01-14 Thread Peter Taoussanis
Just throwing in here that I was actually bit by IKVReduce just today. I swapped a reduce with a reduce-kv, assuming the two would function similarly. And, unfortunately, they did in the testing environment: it took a trip to production before a nil came up. The current behavior is certainly

CollReduce and IKVReduce for nil?

2013-01-12 Thread Wolodja Wentland
Hi all, I was wondering if there is some reason why CollFold and IKVReduce are not extended to nil. A patch for this rots away in JIRA [0] and could probably be merged as-is. Is this simply an oversight or a conscious design decision? [0] http://dev.clojure.org/jira/browse/CLJ-1098 -- Wolodja

Re: CollReduce and IKVReduce for nil?

2013-01-12 Thread Andy Fingerhut
I have no inside information on whether it is an oversight or a conscious design decision, but there are other possibilities besides those two. The CLJ-1098 ticket was categorized as a minor enhancement when it was created. Defects (i.e. bugs) are considered with higher priority. Also Clojure