Shubhamkar Ayare

Ah, yes, blend looks more suitable for this, and much more efficient as well! This brings up another problem I haven't thought about: might there be a way to generate...

This repository looked unmaintained, so I did not create a PR. I also just ended up finding out koji-kojiro has been out of github from 2021 :(. Regardless, people can...

I'm okay issuing PRs to @fukamachi's fork - no need to add me as a maintainer. But if fukamachi could be busy sometimes, I can certainly lend a helping hand...

I don't see a con of maintaining cl-repl under lisp-maintainers. So, I'm okay with that too - might even prefer that way.

In that case, I can transfer the ownership of my fork to lisp-maintainers and cherry-pick fukamachi's commits.

Done: https://github.com/lisp-maintainers/cl-repl

Currently, `with-lispifiers` and `*lispifiers*` is indeed the way to go. It's experimental, because I (or anyone?) haven't tried or thought much about this. However, these run *after* a lisp object...

Lispifying is mainly for converting foreign objects (python objects) into lisp objects, which may be helpful for interfacing with other lisp functions and libraries. I won't consider lispifying hash table...

> boolean constants Do you mean CL booleans or Coalton booleans? If the former, could you provide a sample code where they get used in Coalton code?

Is [ocicl](https://github.com/ocicl/ocicl) an option? I have seen one of my gitlab packages (the only one) being available on ocicl. ([Request additions here](https://github.com/ocicl/request-system-additions-here).) I have a wish list for a conda-lisp...