News for hackers. Stuff that matters.
Re:Google Common Lisp style guide by aidenn0 on Tuesday July 07, 2020 @03:37PM (#23763144)
Right; all abstractions are only as good as they don't leak, but the question is "how easy is it to debug when it does leak?"

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.

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.
Re:Google Common Lisp style guide by aidenn0 on Tuesday July 07, 2020 @06:05PM (#23764638)
Yes, this is a useful tool; I still maintain that debugging macros with this tool is harder than debugging functions with the various other SLIME tools.