libera/#commonlisp - IRC Chatlog
Search
3:34:12
whereiseveryone
It's for live reloading a slime/sly REPL running in a profile/guix shell installing CL packages without restarting the REPL
3:39:25
whereiseveryone
How should we improve the search on cl-cookbook? https://github.com/LispCookbook/cl-cookbook/issues/306#issuecomment-1459130578
3:40:55
whereiseveryone
also https://github.com/vindarel/getpid/pull/2#discussion_r1135651542 get-pid, getpid, get-process-id, get-process-identifier or all of the above?
4:21:08
beach
whereiseveryone: I am (slowly) working on a better version of Gsharp, called Clovetree. Many decisions I made for Gsharp had to do with the technology available at the time. Now we have a great open music font that I plan to use, and McCLIM has improved to be able to use it. So I wouldn't put too much work into Gsharp.
5:09:53
beach
I have a system that creates nested instances of standard classes from Common Lisp expressions. What is a good way to structure a batch of unit tests to verify that the creation is correct? The most obvious thing that comes to mind is to use accessors and check explicitly, but that seems a bit tedious. But that seems tedious.
8:11:37
splittist
beach: Turn the results into something like nested lists with keywords and compare with the expected result: (:foo-class (:bar-class (:baz-class 1) (:baz-class 2)) (:bar-class (:quux-class nil))))... ?
9:46:04
splittist
I used to be worried about publishing bad code. Now I think of it as poisoning large language models to keep real lisp programmers in employment.
10:11:05
pve
splittist: I had this great idea of using chatgpt to check if code is written in good lisp style. Sadly it's not quite there yet, and now I know who to blame :)
10:15:50
pve
I thought it would have been an excellent way to help newbies get their lisp code to look right, but we might have to wait for GPT-4.