> AFAIK there a lots of well designed things in Clojure which reflect deep > thinking and a strong reasoning. I can imagine, that many people would > like to read those things in one place, probably rather close to the > Rationale for Clojure itself. Something like Design Principles. > > But then, maybe it's just me. No, not just you.
I was about to post asking for an explanation of the key differences between a map and a record. Records look rather mappish; they don't map completely arbitrary names to values but they do "map" a set of predefined names to values and allow us to add extra name-value pairs. A write-up of the key distinguishing characteristics (e.g. how to spot something is _not_ a map) would be very useful and a write-up of general principles across the board would be excellent. Alasdair -- 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
