But recur does not do that. Recur does not call a function at all. It is the opposite of calling a function, it says “I want to loop, without the overhead of calling a function and creating a stack frame.” Recur is even used outside of functions entirely; it is how you iterate using the (loop ...) form, and that is almost always how I have used it.
If you want to call a different arity of your function, that has to be an actual function call. recur is only a way to branch back to where you started a loop, or a particular function body. On Tuesday, April 19, 2016 at 10:18:40 AM UTC-5, andmed wrote: > > Thank you. That the point. If "recur" binds to fn, why it can not know the > binding point as the function method based on the number of arguments > passed to it? I mean it is clear that Clojure can't do that, but I can see > no reason why it could or should not if we choose to implement such > syntactic nicety as recur in a function > -- 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/d/optout.
