> In practice, I haven't seen a significant speed improvement in the new branch > of Clojure (except on specific benchmarks that intentionally test Clojure's > new default primitive math). In my day-to-day code, all my numbers, despite > being perfectly small enough to fit in a long, end up getting stored and > retrieved from Clojure's various data structures - vectors, maps, sets, etc. > and thus lose their primitiveness. So I presumably haven't seen any speed > improvement because all the numbers are boxed by the time I do math on them. > Fortunately, I also don't seem to run into arithmetic overflows because my > production code isn't particularly math intensive, but I still end up feeling > stressed out trying to convince myself that it can't ever overflow for any > input.
Mark nails it. The interesting thing about the numeric change in 1.3 is that a great deal of application code is unaffected in *either* direction! That is, (1) It isn't a lot faster. (2) Very little breaks. -- 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
