Re: Calling `str' on a LazySeq

2009-03-22 Thread David Sletten
On Mar 21, 2009, at 11:30 PM, Mark Triggs wrote: >> > > Yep, that's fine. In my case I was actually relying on the fact that > `str' was effectively doing a `prn-str' because I would later read it > back using `read-string' elsewhere. Calling `prn-str' explicitly > isn't a problem--I just though

Re: Calling `str' on a LazySeq

2009-03-22 Thread Mark Triggs
Hi David, On Mar 22, 5:01 pm, David Sletten wrote: > On Mar 21, 2009, at 1:44 PM, Mark Triggs wrote: > > >   user=> (str (filter even? (range 1 10))) > >   "clojure.lang.lazy...@f1005" > > > Previously this would readably print the contents of the seq and some > > of my code was relying on this.

Re: Calling `str' on a LazySeq

2009-03-21 Thread David Sletten
On Mar 21, 2009, at 1:44 PM, Mark Triggs wrote: > > user=> (str (filter even? (range 1 10))) > "clojure.lang.lazy...@f1005" > > Previously this would readably print the contents of the seq and some > of my code was relying on this. Obviously it's not difficult to call > `prn-str' myself, but

Calling `str' on a LazySeq

2009-03-21 Thread Mark Triggs
Hi all, Moving my existing code across to the new lazy trunk, I noticed a very small change: user=> (str (filter even? (range 1 10))) "clojure.lang.lazy...@f1005" Previously this would readably print the contents of the seq and some of my code was relying on this. Obviously it's not diffic