Shubhamkar Ayare

467122112bebdd288a768f4f1937f2dbfd125223 fixes the recent crashing. Some changes to the tests are still required to handle the readtable case correctly. I will ping once those are ready. Although, py4cl2-cffi should itself...

Sorry, I missed the previous message. I myself am primarily an SBCL user and only have a Personal Edition of LispWorks. I don't think that lets me consult LispWorks support....

Nope, we should not use `raw::free-an-object`. In fact, there's no appropriate function for the task. ([Ref](https://mailman3.common-lisp.net/hyperkitty/list/[email protected]/thread/O4BJDU2KXYL7EWQVRR4JC2GQ7K5F3HSJ/).) Playing around, I can confirm that LispWorks can garbage collect the statically allocated vector...

Oh yes, certainly! I already have a [wrapper around static-vectors for dense-arrays](https://github.com/digikar99/dense-arrays/blob/main/plus/static-vectors.lisp). But if I understand, static-vectors itself intends to be portable :). So, I can leave this portability up...

Are there any conventions about reusing existing library names? Say, `cl-utilities` - deprecate the symbols redundant with alexandria, and reexport the symbols from these packages?

Excluding [trivial-garbage](http://quickdocs.org/trivial-garbage/), since I don't think it fits in the sense of utilities used here. Suggest if otherwise.

[Added all except arrows](https://github.com/digikar99/common-lisp.readthedocs/commit/03a91ac67dfda74bd007f1b19390f54beb43813f) - see the linked issue on arrows.

Perhaps, [cl-environments](http://quickdocs.org/cl-environments/) as well - or [introspect-environment](http://quickdocs.org/introspect-environment/)? Nope. Not small.

[trivial-raw-io](https://www.reddit.com/r/lisp/comments/15ff36/is_there_a_recommended_termio_interface_for_cl/) is unmaintained

For the most part, the documentation is taken from the docstrings. (alexandria and postmodern are an exception atm.) However, there does go much manual efforts in hyperlinking or formatting, due...