Yes Anand, I'm worried about that. What I think the solution should be is to allow mutability in the implementation of algorithms in the java back end for the reasons you mentioned, but a clean immutable interface on the clojure side. When users are faced with serious memory limitations, though, that could be a problem. The question is whether that sacrifice is worth the cleanliness of immutability.
-Adler On May 15, 12:33 pm, Anand Patil <anand.prabhakar.pa...@gmail.com> wrote: > On Sat, May 9, 2009 at 7:09 PM, aperotte <apero...@gmail.com> wrote: > > > It shouldn't be a problem to maintain immutability and also perform a > > cross/cartesian product. I'm not sure I understand the problem. > > It was a pretty bad example... what I meant was, in scientific computing, > people often have to take a deep breath and mutate because of speed or > memory limitations. It would be nice to be able to 'unlock' the immutability > somehow if you really need to. > > Anand --~--~---------~--~----~------------~-------~--~----~ 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 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 -~----------~----~----~----~------~----~------~--~---
