On Thursday, September 11, 2014 2:41:44 AM UTC-5, Arnout Roemers wrote: > > I can understand why something like a clojure.lang.Volatile can be useful > for some optimizations in the functions of standard library, but do they > really need to become part of the public core API? >
>From my own perspective (not talking for anyone else here), Clojure is a language that *empowers* you by giving you powerful, composable, expressive tools to solve hard problems. There are guidelines for use but pushing past those guidelines is ok (and expected) as your skills increases or as problems demand it. In this case my general guideline would be: don't use volatiles. Just like learning a musical instrument, learning how best to use the language (and when to break the rules) takes time and practice. -- 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 --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
