It is my experience also, that inlining gives the greatest performance gain for functions that expect primitive arguments. As Chouser said, doing this eliminates the boxing/unboxing overhead.
Here's my take on this: The Java method signatures created by Clojure will always be Objects in order to maintain a consistent interface. Therefore it doesn't make sense for HotSpot to remove that boxing overhead. HotSpot sees a "function that takes a Integer". Why should it eliminate the boxing and treat it like a "function that takes a int"? What if the function really did want a Integer instead of an int? This isn't a decision the compiler can make. Hope that helps (and is correct). -Patrick --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
