Re:Google Common Lisp style guide
by fiddlerwoaroof on Tuesday July 07, 2020 @04:11PM
(#23763446)
In emacs, the macrostep expander solves most of the Macro debugging issues: you usually can expand a macro use, and see exactly what code is being generated or “refactor” the macro away by copying the expansion at a certain level of detail and replacing the original form with it.
I think you listed classes, functions, and named constants in approximately the order of debugability too.
It can be unclear even which macroexpansions are in play from a backtrace, much less which one caused the breakage. (non inlined) functions are right there in the backtrace, and of course, debugging a named constant is as simple as typing its name into the REPL.