top | item 44381862 (no title) dmkolobov | 8 months ago If I had to guess:1. lack of native GC, you had to roll your own by providing a runtime.2. lack of tail-call elimination in V1 of the spec. This essentially forces you to trampoline everything. discuss order hn newest stassats|8 months ago > lack of tail-call eliminationBut lisp doesn't need TCO. dreamcompiler|8 months ago Common Lisp doesn't technically require TCO but Scheme does.IMHO a Common Lisp without TCO is not a serious tool because I cannot write tail-recursive code with it. load replies (1) bevr1337|8 months ago Whoa, what a surprising fact! I had not considered TCO in LISP was "nice to have." That's a good example where it's easy to hack but hard to make production ready.
stassats|8 months ago > lack of tail-call eliminationBut lisp doesn't need TCO. dreamcompiler|8 months ago Common Lisp doesn't technically require TCO but Scheme does.IMHO a Common Lisp without TCO is not a serious tool because I cannot write tail-recursive code with it. load replies (1) bevr1337|8 months ago Whoa, what a surprising fact! I had not considered TCO in LISP was "nice to have." That's a good example where it's easy to hack but hard to make production ready.
dreamcompiler|8 months ago Common Lisp doesn't technically require TCO but Scheme does.IMHO a Common Lisp without TCO is not a serious tool because I cannot write tail-recursive code with it. load replies (1)
bevr1337|8 months ago Whoa, what a surprising fact! I had not considered TCO in LISP was "nice to have." That's a good example where it's easy to hack but hard to make production ready.
stassats|8 months ago
But lisp doesn't need TCO.
dreamcompiler|8 months ago
IMHO a Common Lisp without TCO is not a serious tool because I cannot write tail-recursive code with it.
bevr1337|8 months ago