3 ms·
Ugly hack ... but maybe a useful one? In that explicitly requesting TCO avoids certain classes of errors? (I don't know on balance, haven't tried TCO in Cloju
by hga 13y ago
Ugly hack ... but maybe a useful one? In that explicitly requesting TCO avoids certain classes of errors? (I don't know on balance, haven't tried TCO in Clojure in anger, and I experience enough value in being in the JVM ecosystem that it's a price I'm in theory willing to pay for now.)
The problem with CL is that you can't assume it in every major implementation. Although I just found this page which paints a fairly good picture: http://0branch.com/notes/tco-cl.html http://0branch.com/notes/tco-cl.html
"The following implementations were found to provide full TCO:
CMUCL
SBCL
CCL
Allegro
LispWorks
…only optimise self-calls in tail position:
CLisp
GCL
ECL (when explicitly compiled)
…neither:
ABCL
Back to me: and CL is so big that "non-major" ports are of much less interest.
As for vector, map and set syntax, that was explicit mentioned as being a surface thing. The real special sauce is in how they've been unified with lists, especially under the hood.
As for your last point, I see great value in all that in the LISPs, although I of course prefer Scheme. But I also see great value in the "Lisp" (LISt Processing no longer the alpha and omega) in what Clojure is doing."