debug icon indicating copy to clipboard operation
debug copied to clipboard

a racket lang-extension for debugging, and a macro for inserting a debug-repl

Results 6 debug issues
Sort by recently updated
recently updated
newest added

When instrumenting calls to recursive functions, it's hard to tell which calls match which returns. Showing the value of the arguments in addition to / instead of the instrumented form....

The ability to disable debug (or otherwise override debug's behavior) at runtime would be a great feature. Downside: it might encourage people to start committing code with `#R` all over...

Sometimes I don't want to debug an expression, I want to debug all calls to a particular function. Would that belong in this package or a different library? I'm imagining...

Compiling `debug` currently fails due to [the use of 3D syntax in `debug/repl.rkt`](https://github.com/AlexKnauth/debug/blob/0424641fce57efb915d12e6576b8c87aef7a826a/debug/repl.rkt#L42-L46). I see the purpose of this, and it does appear to work as long as the code...

Within a `(debug-repl)`, I want to the local variables accessible within it to be immutable. By that I mean using `set!` on them should fail.

On my system, after entering the debug repl and interacting, I don't seem to see output. I press return at the end of line. User error? ![image](https://github.com/AlexKnauth/debug/assets/1329370/a4e30a0c-75bf-4835-b18e-104a9fd2f4cc)

bug