On May 28, 2010, at 12:42 PM, Laurent PETIT wrote: > The rule should really always be: no warning at all (with > *warn-on-reflection* set to true, of course).
I strongly disagree. Why should you care about those sorts of warnings unless you've already identified a bottleneck that needs elimination? IMO the "rule" should be: write it the simplest way you can first, then optimize only what your benchmarks tell you needs optimizing. -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to [email protected] Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/clojure?hl=en
