Hi, On 3 Nov., 15:37, Mark Hamstra <markhams...@gmail.com> wrote:
> It would seem that a solution to this problem would be to treat such > automatic boxing/upcasting similar to reflection -- i.e., have an > option that causes Clojure to spit out a warning when such boxing/ > upcasting occurs, alerting the performance conscious of the need to > change the code that is generating the offense. At least for loop this happens when *warn-on-reflection* is true. Sincerely Meikel -- 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
