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
Would be nice to have full featured repl experience within the debugger. Being able to freely eval arbitrary forms and instrument other forms within the debugger is very useful. Also see this comment.
There are two ways to go about it. Either mimic interruptible-eval within the debugger (might be easier with the current implementation), or recur to some async strategies (e.g. allocate for each debugged session its own thread and stall that one instead of the eval thread). The second strategy would mean a more complicated instrumentation of def forms, like wrapping def's bodies into futures or async go blocks.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contribution and understanding!
Would be nice to have full featured repl experience within the debugger. Being able to freely eval arbitrary forms and instrument other forms within the debugger is very useful. Also see this comment.
There are two ways to go about it. Either mimic
interruptible-eval
within the debugger (might be easier with the current implementation), or recur to some async strategies (e.g. allocate for each debugged session its own thread and stall that one instead of the eval thread). The second strategy would mean a more complicated instrumentation ofdef
forms, like wrapping def's bodies into futures or async go blocks.The text was updated successfully, but these errors were encountered: