3 ms·

Fast SEQUENCE iteration in Common Lisp

vindarel 10mo ago
The same day, after this post, SBCL's main developer made reduce faster (https://www.reddit.com/r/lisp/comments/1pmip8o/fast_sequence_iteration_in_common_lisp/ https://www.reddit.com/r/lisp/comments/1pmip8o/fast_sequence...). Let's see on the next SBCL release what the final results are.
- themafia 10mo 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 10mo 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
    - CyberDildonics 10mo ago
      It has only been 68 years, give it a little more time.
matheusmoreira 10mo 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 10mo ago
  As linked, the extensible sequence protocol (https://shinmera.com/docs/trivial-extensible-sequences/ 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.
  - shawn_w 10mo 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.
  - stackghost 10mo 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
    - a-french-anon 10mo ago
      Personally, I still try to support CCL, ECL and CLISP in addition to SBCL; I mostly ignore CLISP's warnings though.
    - deleted 10mo ago
      [deleted]
    - guenthert 10mo ago
      > CCL, as far as I can tell, is abandonware Last release was August 14 2024. For a 30+ year old project, that's quite recent methinks. It clearly doesn't move as fast as SBCL, but I wouldn't call it abandoned either. ototh, afaiu, SBCL gave up on ARM32. Can't blame them for that, but until 2023 I was still using an early Banana Pi with such. CCL worked there much better (also it's GC seems more robust).
    - 10mo ago
ezoi_MuUJd 10mo ago
[flagged]
tug2024 10mo ago
[dead]

The same day, after this post, SBCL's main developer made reduce faster (https://www.reddit.com/r/lisp/comments/1pmip8o/fast_sequence_iteration_in_common_lisp/ https://www.reddit.com/r/lisp/comments/1pmip8o/fast_sequence...). Let's see on the next SBCL release what the final results are.

themafia 10mo 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 10mo 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
  - CyberDildonics 10mo ago
    It has only been 68 years, give it a little more time.

matheusmoreira 10mo 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 10mo ago
As linked, the extensible sequence protocol (https://shinmera.com/docs/trivial-extensible-sequences/ 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.
- shawn_w 10mo 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.
- stackghost 10mo 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
  - a-french-anon 10mo ago
    Personally, I still try to support CCL, ECL and CLISP in addition to SBCL; I mostly ignore CLISP's warnings though.
  - deleted 10mo ago
    [deleted]
  - guenthert 10mo ago
    > CCL, as far as I can tell, is abandonware Last release was August 14 2024. For a 30+ year old project, that's quite recent methinks. It clearly doesn't move as fast as SBCL, but I wouldn't call it abandoned either. ototh, afaiu, SBCL gave up on ARM32. Can't blame them for that, but until 2023 I was still using an early Banana Pi with such. CCL worked there much better (also it's GC seems more robust).
  - 10mo ago

ezoi_MuUJd 10mo ago

[flagged]

tug2024 10mo ago

[dead]