On Wed, Jun 13, 2012 at 1:52 AM, Vinzent <ru.vinz...@gmail.com> wrote: > Why do you care about computational expensiveness of pre and post > conditions? They'll be turned off in production anyway.
I think that's a philosophical question :) > In clojure, structure of your map is a part of the contract. It's not an > implementation detail - it's the same as getters\setters in java. I agree. Focusing on data-as-API is a tough shift for a lot of people coming from an OO background but it's important. Stuart Halloway's talk at Clojure/West (about the design of Datomic) made some good points on this topic. > Well, this is a contrived example, since you'd use a plain string instead of > a map with the single :value key :) Given that, user and domain would > probably be functions. Agreed. And that's part of the shift I'm talking about. -- Sean A Corfield -- (904) 302-SEAN An Architect's View -- http://corfield.org/ World Singles, LLC. -- http://worldsingles.com/ "Perfection is the enemy of the good." -- Gustave Flaubert, French realist novelist (1821-1880) -- 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
