4 comments

  • vindarel16 hours ago
    The same day, after this post, SBCL&#x27;s main developer made reduce faster (<a href="https:&#x2F;&#x2F;www.reddit.com&#x2F;r&#x2F;lisp&#x2F;comments&#x2F;1pmip8o&#x2F;fast_sequence_iteration_in_common_lisp&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.reddit.com&#x2F;r&#x2F;lisp&#x2F;comments&#x2F;1pmip8o&#x2F;fast_sequence...</a>). Let&#x27;s see on the next SBCL release what the final results are.
    • themafia15 hours ago
      Stas is a machine. Almost every single day he&#x27;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.
      • stackghost11 hours ago
        SBCL is a treasure. I really enjoy writing lisp, I just wish the library ecosystem was a little more mature.<p>I still use it whenever I can
        • CyberDildonics9 hours ago
          It has only been 68 years, give it a little more time.
  • matheusmoreira15 hours ago
    &gt; sequences are a band-aid over the lack of real iterator protocol<p>Wouldn&#x27;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.
    • BoingBoomTschak15 hours ago
      As linked, the extensible sequence protocol (<a href="https:&#x2F;&#x2F;shinmera.com&#x2F;docs&#x2F;trivial-extensible-sequences&#x2F;" rel="nofollow">https:&#x2F;&#x2F;shinmera.com&#x2F;docs&#x2F;trivial-extensible-sequences&#x2F;</a>) already exists and is quite workable. The problem is that it&#x27;s not supported enough, both by implementations (CCL missing, for example) and the entire ecosystem.<p>In the end, it&#x27;s simpler to stay with boring, ANSI compliant solutions well optimized by compilers.
      • shawn_w12 hours ago
        I&#x27;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&#x27;m not sure it&#x27;s worth the effort.
      • stackghost11 hours 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.<p>CCL, as far as I can tell, is abandonware
        • guenthert2 hours ago
          &gt; CCL, as far as I can tell, is abandonware<p>Last release was August 14 2024. For a 30+ year old project, that&#x27;s quite recent methinks.<p>It clearly doesn&#x27;t move as fast as SBCL, but I wouldn&#x27;t call it abandoned either.<p>ototh, afaiu, SBCL gave up on ARM32. Can&#x27;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&#x27;s GC seems more robust).
        • tmtvl2 hours ago
          ECL still has its niches (if you want to use CL in an Android application, for example, ECL is easier to work with than SBCL).
        • a-french-anon6 hours ago
          Personally, I still try to support CCL, ECL and CLISP in addition to SBCL; I mostly ignore CLISP&#x27;s warnings though.
  • tug20249 hours ago
    [dead]
  • ezoi_MuUJd13 hours ago
    [flagged]