It would be nice if patches were accompanied by failing (and after patching, fixed) tests so that we can get a higher level of formalism and confidence out of both clojure and clojure.contrib. These tests would also be good lessons for newer people about some of the gotchas with lazy eval.
Chris On Feb 16, 10:23 am, Stuart Sierra <the.stuart.sie...@gmail.com> wrote: > I created a lazy branch of clojure-contrib to track patches to contrib > that are needed in the lazy branch of Clojure. > > For clojure-contrib hackers: > svn checkouthttps://clojure-contrib.googlecode.com/svn/branches/lazy > clojure-contrib-lazy --username your.google.account > > For everyone else: > svn checkouthttp://clojure-contrib.googlecode.com/svn/trunk/clojure- > contrib-lazy > > -Stuart Sierra --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
