Readit News logoReadit News
vindarel · 2 days ago
The same day, after this post, SBCL's main developer made reduce faster (https://www.reddit.com/r/lisp/comments/1pmip8o/fast_sequence...). Let's see on the next SBCL release what the final results are.
themafia · 2 days ago
Stas is a machine. Almost every single day he's in the sources making improvements. I joined the sbcl-commit list recently and the project is far more active and cared for than I had originally suspected.
stackghost · 2 days ago
SBCL is a treasure. I really enjoy writing lisp, I just wish the library ecosystem was a little more mature.

I still use it whenever I can

matheusmoreira · 2 days ago
> sequences are a band-aid over the lack of real iterator protocol

Wouldn't it be better to solve that problem? Proper generalized iteration with generators is just semicoroutines which can be implemented by swapping around stack pointers with zero copying. Should be competitive performance wise.

BoingBoomTschak · 2 days ago
As linked, the extensible sequence protocol (https://shinmera.com/docs/trivial-extensible-sequences/) already exists and is quite workable. The problem is that it's not supported enough, both by implementations (CCL missing, for example) and the entire ecosystem.

In the end, it's simpler to stay with boring, ANSI compliant solutions well optimized by compilers.

stackghost · 2 days ago
There are effectively two Common Lisp worlds: the commercial world where Allegro and Lispworks dominate, and the non-commercial world where SBCL is more or less the only game in town.

CCL, as far as I can tell, is abandonware

shawn_w · 2 days ago
I've been toying with trying to add extensible sequences to ccl as a way to get more familiar with it, but ccl development seems dead so I'm not sure it's worth the effort.

Dead Comment

Dead Comment