Re: pr-str and safe serialization

2015-07-25 Thread xavi
Hello, I also stumbled on this bug. Here's a simple example showing the problem... (def a (pr-str (map (fn [i] (println hi) i) [1]))) After executing that code I was expecting the value of `a` to be `(1)`, but instead the actual value is `(hi\n1)`. Xavi On Thursday, June 25, 2015 at

pr-str and safe serialization

2015-06-24 Thread Ignacio Thayer
I think this might be rehashing some old stuff, but I haven't seen discussion on it recently and I see this behavior is still present in 1.7 so I thought I'd ask. It's the same underlying issue as this:

Re: pr-str and safe serialization

2015-06-24 Thread Fluid Dynamics
On Wednesday, June 24, 2015 at 4:56:06 PM UTC-4, Ignacio Thayer wrote: I think this might be rehashing some old stuff, but I haven't seen discussion on it recently and I see this behavior is still present in 1.7 so I thought I'd ask. It's the same underlying issue as this:

Re: pr-str and safe serialization

2015-06-24 Thread Matching Socks
There are currently no votes for either Jira issue! - No.1532, pr-str captures stdout from printing side-effects of lazily evaluated expressions - No.1611, clojure.java.io/pushback-reader -- You received this message because you are subscribed to the Google Groups Clojure group. To post to