I'm working on the latter right now.  Note there's already a ticket
for the reflection problem:
https://www.assembla.com/spaces/clojure/tickets/446


On Oct 1, 12:24 pm, Nicolas Oury <nicolas.o...@gmail.com> wrote:
> > David pointed out what should have been the obvious overhead (I'll
> > blame it on being up at 2am), and Nicolas pointed out the specific
> > problem.
>
> two solutions:
>
>   - writing all combinations of unboxed/boxed for every function
>   - having a more clever code generator that try to box every
> primitive if it allows to prevent a reflective call.
>     (And maybe emit a "boxing warning")

-- 
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

Reply via email to