Live data from Hacker News

Ask HN: If you were designing Common Lisp today, what would you change?

news.ycombinator.com

31–32 of 32 posts

Re: Ask HN: If you were designing Common Lisp today, what would you change?

#31

Earlier quoted context omitted.

> basic' loop in lisp is tree/heap traversal from initial outer (). That's completely false, except that loops can be used to code a tree traversal. Looping is a control construct centered around a backward branch, updates to iteration variables and termination testing. Loops can compile code that has nothing to do with the heap.

Why prefer a non-functional construct over a functional construct in a functional language? The lisp loop macro simplifies the s-expression tree/heap traversal for benifit of coder/reader. The lisp loop macro is implilmented based on s-expression tree traversal. Trees are used with closures. Heaps are used with objects. (lisp & non-lisp) In lisp can debate what's an 'object', but multiple thunks are managed through a…

Today's forecast is partly kooky, with 80% chance of bot.

Re: Ask HN: If you were designing Common Lisp today, what would you change?

#32

Earlier quoted context omitted.

Why prefer a non-functional construct over a functional construct in a functional language? The lisp loop macro simplifies the s-expression tree/heap traversal for benifit of coder/reader. The lisp loop macro is implilmented based on s-expression tree traversal. Trees are used with closures. Heaps are used with objects. (lisp & non-lisp) In lisp can debate what's an 'object', but multiple thunks are managed through a…

Today's forecast is partly kooky, with 80% chance of bot.

Kazinator, suggested Lisp conference(s) to submit relevant paper(s) to so can cover travel expenses to prove not a bot?
Post reply on HN