News for hackers. Stuff that matters.
Re:One Major Difference Between Clojure and Common Lisp by treerex on Saturday September 12, 2015 @07:46PM (#10209790)
Yes, silent TCO. Isn't that what most people mean about TCO when applied to recursion?
Re:One Major Difference Between Clojure and Common Lisp by hga on Saturday September 12, 2015 @08:40PM (#10209930)
Perhaps, but that doesn't mean it's accurate. TCO literally just says tail calls are optimized, and I personally see an advantage to making your intent to make a TCO-ed tail call explicit, so like in Clojure you get a compilation error rather than blowing your stack at runtime.

It certainly looks more elegant to do it silently, but Clojure doesn't strive for that sort of elegance.

Re:One Major Difference Between Clojure and Common Lisp by dkersten on Sunday September 13, 2015 @06:44PM (#10213036)
TCO is broader than what recur does. Recur only optimises recursive tail-calls to the function you are in, TCO generally implies that any tail-calls (recursive or not) can be optimised (including mutually recursive calls, for which clojure made the trampoline function or just calling one function at the tail of another).

Personally, I like clojure's approach as IMHO recur makes intent clear, but recur is a subset of what TCO optimises in other languages.