On Aug 14, 2009, at 8:53 PM, Mark Volkmann wrote:
> So it seems the biggest impact of the change can be summarized as > follows. In the past, once you successfully ensured a Ref, you knew > you could write to it later because no other thread could also ensure > it. Now you don't know that. You know you can stop other threads from > writing the Ref, but you won't be able to write the Ref as long as > other threads have also ensured it. > > I'm not criticizing the change. There were likely good reasons for it. > > Please let me know if I have interpreted anything incorrectly. Totally aside from the correctness of that analysis (which I've no reason to doubt a.t.m.), I just want to clarify that I never actually encountered any deadlocks (though I absolutely did burn a bunch of cycles trying to figure out why some fn was seeing old values in certain refs...due to the fn being involved in a pmap over a series of objects that contained refs). - Chas --~--~---------~--~----~------------~-------~--~----~ 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, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
