3:20:39beachElronnd: In the Cleavir compiler, we represent source programs using "Concrete Syntax Trees", or CSTs: https://github.com/robert-strandh/Concrete-Syntax-Tree
3:21:07beachElronnd: The main purpose is to keep source information that we can propagate through the various steps of compilation.
3:26:48LdBethbeach: if it's allowed for a CL compiler to reject code that will produce a runtime error
3:30:23beachGood question. I don't recall having seen anything about that in the Common Lisp HyperSpec.
3:31:10pjbLdBeth: Not really. Because you can call the function that produces the run-time error with a handler-case, and expect the condition.
3:32:11pjbLdBeth: on the other hand, if the compiler can determine at compilation-time that an error would always be produced at run-time, it can generate only the code that signals the error.
3:32:23pjb(and not the code that would produce the error).
5:29:52aethXach: What do you use to fail on warnings in your Quicklisp tests? asdf:*compile-file-warnings-behaviour*? How do you handle packages that conflict with each other? Do you have to build each project one at a time, restarting between each build?