> It's a consequence of immutable data structures, which are an aspect of > functional programming. An immutable object can never be changed
But single-assignment is a quite valid (and more flexible?) form of immutability. I'm not convinced cycles are intrinsically tied to it in any way. (In fact, I initially thought Clojure had an unambiguous sentinel value for "not initialized") I was hoping to develop (or find :) macros to automate the code for maintaining various kinds of 2-way pointers, rather than use separate ID fields or (essentially global) collections of pairs for relations. -- 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 To unsubscribe, reply using "remove me" as the subject.
