Re: Bug in printing futures

2012-10-13 Thread AtKaaZ
Hi S, that's encouraging, I've to admit I've been poking at this for a few hours now, but I'm not as productive as the (real)programmers. I've yet to read the following which is a how to submit patches: http://dev.clojure.org/display/design/JIRA+workflow Meanwhile poking around, I've found the

Re: Bug in printing futures

2012-10-12 Thread Stuart Sierra
Patch welcome. -S -- 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 Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group,

Bug in printing futures

2012-10-11 Thread Dave Ray
In Clojure 1.4, I came across the following this week: user= (def f (future (Thread/sleep 2))) #'user/f user= f #core$future_call$reify__6110@27adc5f7: :pending user= (future-cancel f) true user= f CancellationException java.util.concurrent.FutureTask$Sync.innerGet

Re: Bug in printing futures

2012-10-11 Thread AtKaaZ
I notice it happens on Clojure 1.5.0-master-SNAPSHOT also. Calling something like: (future-cancelled? f) *true* before getting @f makes sense, but since I'm a clojure newb I don't know what showing f (not @f) would show. Maybe it should show something like: #core$future_call$reify__3499@7c9391d9: