Good. I was worried I'd be forced over to the Lazy branch before I was
ready. :)
On Mon, Feb 16, 2009 at 4:05 PM, Stephen C. Gilardi wrote:
>
> On Feb 16, 2009, at 3:52 PM, Jeffrey Straszheim wrote:
>
> Isn't that second url just the normal one for contrib trunk?
>>
>
> Yes, you should replace
On Feb 16, 3:52 pm, Jeffrey Straszheim
wrote:
> Isn't that second url just the normal one for contrib trunk?
Oops, sorry.
svn checkout http://clojure-contrib.googlecode.com/svn/branches/lazy/
clojure-
contrib-lazy
--~--~-~--~~~---~--~~
You received this message b
On Feb 16, 2009, at 3:52 PM, Jeffrey Straszheim wrote:
Isn't that second url just the normal one for contrib trunk?
Yes, you should replace "trunk" with "branches/lazy" there as well.
--Steve
smime.p7s
Description: S/MIME cryptographic signature
Isn't that second url just the normal one for contrib trunk?
On Mon, Feb 16, 2009 at 12:23 PM, Stuart Sierra 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 checkout https://
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
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 checkout https://clojure-contrib.googlecode.com/svn/branches/lazy
clojure-contrib-lazy --username your.google.account
For everyone else:
svn chec
