I ran into something else interesting, maybe just a known limitation, but feels like it severely limits the usefulness of being able to execute code at breakpoints: https://gist.github.com/adamrenklint/497d6db755eba21b965ee56f610314b8

When I call a function that contains a breakpoint from the REPL, I am not able to call any other functions from the REPL while stopped at that breakpoint.

@adamrenklint aha, thanks for reporting

this probably makes sense, because on server-side, we request-eval from javascript, it stops on a breakpoint and then in dirac prompt we request another code snippet to be evaluated by javascript, but the server-side component can deal only with one request at a time - it processes them in serial queue and still waiting for result of the first eval

https://github.com/binaryage/dirac/blob/master/src/lib/dirac/lib/weasel_server.clj#L197 https://github.com/binaryage/dirac/blob/master/src/lib/dirac/lib/weasel_server.clj#L141

I will probably have to think about this scenario, maybe allow multiple pending eval requests or somehow treat the eval request paused on a breakpoint as “completed”

=> https://github.com/binaryage/dirac/issues/74

feel free to open issues next time