sbcl VS emacs4cl

Based on the commit message [0], and the references to "user code" in this document, my guess is that user programs have or will have access, but it's not finalized enough to be documented.

That being said, I suppose if you're developing an internal API for a compiler/interpreter, your "users" could be other parts of the project rather than language users.

https://github.com/sbcl/sbcl/commit/7f65522a16d857e41aa61cd0...

See for example:

https://github.com/sbcl/sbcl/blob/master/doc/internals-notes...

related: the Immix inspired parallel-mark-region GC developed by Hayley Patton (https://github.com/no-defun-allowed/swcl) got merged recently into SBCL.

https://github.com/sbcl/sbcl/blob/master/doc/internals-notes...

https://applied-langua.ge/~hayley/swcl-gc.pdf

build with

    ./make.sh --without-gencgc --with-mark-region-gc (on x86-64/Linux and x86-64/macOS only at the moment).

The Immix inspired mark-region GC developed by Hayley Patton (https://github.com/no-defun-allowed/swcl) got merged recently, which is pretty cool news for SBCL users.

Yes, indeed. The output of git diff 0.1.0..0.5.0 shows that the bulk of the bloat comes from customising rainbow delimiters to show colourful parentheses.

Here's a good guide: https://github.com/susam/emacs4cl

And the excellent guide to Emacs and SLIME too. https://github.com/susam/emacs4cl

In addition to the great resources mentioned, see this guide: https://github.com/susam/emacs4cl I like it with one difference: keep the Emacs menu bar and use it to explore the available commands.

Hello! Thank you for referring to my Vim + Slimv guide. I have, in fact, two guides to set up a Common Lisp programming environment from scratch:

For Vim: https://susam.net/blog/lisp-in-vim.html

For Emacs: https://github.com/susam/emacs4cl

PPS: There's a much more well maintained and more widely used .emacs script at emacs4cl, plus a number of other resources at awesome-cl#emacs!