> I didn't find any of them compelling enough for core just yet. Putting > them in contrib first lets people try them out and refine them, point > out redundancies and conflicts etc. > > As a general rule I haven't pulled many simple combining functions > from contrib, as they just pollute the namespaces. Plus, I don't think > things are as cut and dried as you make out, for instance I'd expect > map-when and iterate-while to take predicates.
Fair enough, I would be happy with those in contrib. The main things I'd like to see in core are: - 0-arg distinct? returns true, not an exception (so (apply distinct? nil) = true) - rewrite concat so that (apply concat seq) doesn't evaluate the first three elements of seq - make every?, not-every?, some, not-any? take multiple seq args like map, i.e., (every? not= [1 2 3] [2 3 4]) - allow arguments to merge-with after the first to be lists of pairs. More details on each of these are above. None of these affect the existing functionality of these core functions, and it doesn't seem to make sense to create new versions in clojure.contrib just to add the new functionality. Will you accept issues for any of these? Thanks, Jason --~--~---------~--~----~------------~-------~--~----~ 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 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 -~----------~----~----~----~------~----~------~--~---
