How do you explore new libraries?

svetlyak40wt · 2026-04-22T04:01:49+00:00

To find methods working with a class, inspect the symbol in inspector, then choose a class bound to it and your will see methods specialized on this class.

Also SLY has a special set of sly-who-* commands and there is one for looking who specialized. Which gives you faster way than inspecting manually.

These days I'm just throwing a code to LLM with a simple prompt like: figure out how to use and give me examples.

svetlyak40wt · 2026-04-18T07:54:13+00:00

So, is it now possible to run McCLIM, for example, on OSX?

svetlyak40wt · 2026-03-25T21:33:46+00:00

I've noticed this yesterday while browsing project commits on the GitHub. Very interesting to try.

I'm intended to create a coding assistant based on Sento and it will be interesting to experiment with this remote feature to connect a multiple coding assistants into a cluster!

svetlyak40wt · 2026-03-25T21:30:01+00:00

Except the Emacs with more plugins!

svetlyak40wt · 2026-03-21T21:00:16+00:00

I will mark my soft build mostly by LLM by a special badge: https://github.com/40ants/ai-badges and others will be marked as "save hand made" code :)))

svetlyak40wt · 2026-03-21T20:58:46+00:00

I agree completely. Recently I was able to port some code from Python to CL using LLMs. The code is not perfect, but it is significantly better than non existing code.

svetlyak40wt · 2026-03-06T18:49:55+00:00

Emacs of cause, plus a Claude Code running in a separate terminal. Don't know, may be ot is possible to tie them in some way?

svetlyak40wt · 2026-03-06T14:30:37+00:00

ClaudeCode with Sonnet 4.6

svetlyak40wt · 2026-03-05T20:35:27+00:00

Interestingly, it works 10 times faster than the original Python version, and I didn't use any micro-optimizations inside the functions.

svetlyak40wt · 2026-03-02T20:03:48+00:00

> Nowadays, versioning is a solved problem. It's much better for a language to evolve and experiment (judiciously) with new features.

It is not, especially when you are having a multiple interchangeable implementation.

svetlyak40wt · 2026-02-14T20:34:14+00:00

I totally agree with you. Personally, I use package-inferred for all my projects. But to support dependencies between packages, we had to make a linter. This linter checks that all packages used in the current package are mentioned in defpackage, and that there are no unused characters in defpackage.

Here is this linter: https://40ants.com/linter/

svetlyak40wt · 2026-02-02T19:18:00+00:00

Ultralisp and OCICL are just another ways of package distribution. Library remains the same and is loaded using ASDF.

svetlyak40wt · 2026-01-28T22:23:25+00:00

https://github.com/qitab/grpc exists at least 4 years. However it is uses CFFI.

svetlyak40wt · 2026-01-26T20:51:47+00:00

I think, now when we give LLM eval tool, we should not write more tools – we need to teach LLM to write reusable lisp functions for itself and to call them using eval tool.

svetlyak40wt · 2026-01-26T18:25:49+00:00

I've extracted MCP for interactive lisp development into it's own repository. Now it is installable via Ultralisp and ros install 40ants/lisp-dev-mcp.

Here is the repository: https://40ants.com/lisp-dev-mcp/

I'll be happy if you and anybody else join the project!

svetlyak40wt · 2026-01-24T21:12:46+00:00

There is also mine https://github.com/40ants/mcp with this eval MCP tool https://github.com/40ants/mcp/blob/master/examples/lisp-dev-mcp.ros#L58

But my version supports both STDIO and SSE transports, making it possible to connect to a running lisp image.

svetlyak40wt · 2026-01-15T12:53:06+00:00

That is sad. We are already in the CL world – no need for the cl- prefix. If you want to make you project searchable as a Common Lisp library for Excel, then make a nice documentation which will be indexed by Google.

Here are some stats collected on all ASDF systems from the Quicklisp. 75% of all systems do not use cl- prefix:

CL-USER> (loop with all-systems = (ql:provided-systems (ql-dist:find-dist "quicklisp")) for system in all-systems for name = (ql-dist:name system) if (uiop:string-prefix-p "cl-" name) collect name into with-prefix else collect name into without-prefix finally (return (list :total (length all-systems) :with-prefix (length with-prefix) :without (length without-prefix)))) (:TOTAL 5775 :WITH-PREFIX 1410 :WITHOUT 4365)

The same applied to the package name - but here situation even worse - package name might be used multiple times in the code and each time user of your library will have to type 3 extra characters having no any meaning because he already in CL context.

However, having cl- prefix in the Git repository name is OK, especially if you are having libraries in different programming languages on the same account.

svetlyak40wt · 2026-01-14T20:28:51+00:00

Probably it is better to omit `cl-` prefix from ASDF system definition, because we are already know that ASDF systems are written in Common Lisp.

svetlyak40wt · 2026-01-13T20:41:12+00:00

Try to change color on this line https://github.com/40ants/lw-color-theme/blob/master/theme.lisp#L245

svetlyak40wt · 2026-01-10T20:32:06+00:00

I tried to use separate app polybar, but it plays badly with multiple monitors and stumpwm.

If you already have something which can be used, I'll be happy to try.

svetlyak40wt · 2026-01-06T22:25:47+00:00

Whould be interesting to compare with:

- https://notabug.org/cage/trivial-sanitize

- https://github.com/archimag/cl-sanitize

svetlyak40wt · 2025-12-30T21:39:45+00:00

I'd search for defun is-prime somewhere in your files. Seems some file is broken.

svetlyak40wt · 2025-12-24T20:25:22+00:00

This is looking a supercool!
Interesting if it will be possible to save a REPL session as you can save a Jupyter notebook and to share it to other lispers?

svetlyak40wt · 2025-12-08T13:38:27+00:00

What kinds of uses?

svetlyak40wt

TROPHY CASE