On Tue, Jul 9, 2013 at 10:28 AM, Mikera <mike.r.anderson...@gmail.com>wrote:
>
> A reasonably simple optimisation would be to automatically identify
> self-recursion in tail position and convert it directly to "recur". I think
> that's possibly the kind of optimisation pass that the OP was suggesting.
>
One thing that would be neat, if feasible, would be to make it possible to
do tail call elimination in situations where you can't currently use
"recur" because there's already a target established---if you have
something like
(defn foo [...]
(loop [...]
(if some-condition
(recur ...)
(foo ...))))
where you can't use recur for the call to foo, even though it's in tail
position, because the recur target is the loop expression.
--
Ben Wolfson
"Human kind has used its intelligence to vary the flavour of drinks, which
may be sweet, aromatic, fermented or spirit-based. ... Family and social
life also offer numerous other occasions to consume drinks for pleasure."
[Larousse, "Drink" entry]
--
--
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
---
You received this message because you are subscribed to the Google Groups
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
