...from which variables on the stack can be manipulated, and the program can be resumed with all the stack intact/modified, either before the exception or after, or somewhere else in the same function or maybe higher up in the stack.
I was thinking of doing this as mainly a CLI interface (and to research it enough UX-wise to make it noticeably nice to use), but for once I also see the point of doing it as a GUI interface too. I think the nice thing about that would be that the values in the stack could be visualized and manipulated in quite an intuitive/straightforward way.
Might be nice/useful to be able to save/load the whole stack and the rest of the environment.
Marked as blocked, because there's no use doing this before we have our own runtime. (#377)
...from which variables on the stack can be manipulated, and the program can be resumed with all the stack intact/modified, either before the exception or after, or somewhere else in the same function or maybe higher up in the stack.
I was thinking of doing this as mainly a CLI interface (and to research it enough UX-wise to make it noticeably nice to use), but for once I also see the point of doing it as a GUI interface too. I think the nice thing about that would be that the values in the stack could be visualized and manipulated in quite an intuitive/straightforward way.
Might be nice/useful to be able to save/load the whole stack and the rest of the environment.
Marked as blocked, because there's no use doing this before we have our own runtime. (#377)