5:09:53beachI 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:37splittistbeach: 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:04splittistI 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:05pvesplittist: 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 :)