3 ms·
Usually, people tend to see the following problems: * no native support, hosted language (js java) * unreadable (java) tracebacks * no tail call optimization
by macco 10y ago
Usually, people tend to see the following problems:
* no native support, hosted language (js java)
* unreadable (java) tracebacks
* no tail call optimization
These are not my problems with Clojure, but then things I often read. I am interested in Common Lisp because of the native support.
- markc 10y agoI prefer loop/recur to TCO. You know exactly when you are, and are not, in tail position (which can be a bit obscure) and the compiler won't let you recur from non-tail.
- lispm 10y agoloop/recur handles only a tiny part of TCO. TCO means all calls in tail position are optimised, not just the self-recursive ones. Personally I find loop/recur ugly. It's a partial hack around the lack of TCO. Though I prefer looping statements like Common Lisp's ITERATE, whose design I like a lot... https://common-lisp.net/project/iterate/doc/index.html https://common-lisp.net/project/iterate/doc/index.html