You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are a couple of problems of using slime with lisp unit.
when a test fails and slime displays the stack trace, normally I can press 'v' on the stack trace line to navigate the editor to the line of code. This does not work if the point of breakage is inside a define-test. For some reason lisp-unit does not compile the code in a way which is accessible to slime.
when I press C-c C-c on a test, the compiler does not check the code and present me with the compiler warnings/errors.
The text was updated successfully, but these errors were encountered:
My proposed fix is to profile the macro defun-test, similar to define-test.
The difference is that defun-test defines a function of the same name as the test.
This function compiles as ordinary code, visible to the compiler and the debugger.
The defun-test macro also defines a test via define-test which simply calls the function
of the same name. This way the test is also available to lisp-unit to do whatever it wants
with it.
There are a couple of problems of using slime with lisp unit.
The text was updated successfully, but these errors were encountered: