This repository was archived by the owner on Jul 30, 2021. It is now read-only.
How to stop run of program right before fixpoint calculation #24
Comments
|
Reassigning to the second release as this would bring new functionality. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When finding out why fixpoint is not yet reached, you need to see the state of program right before the fixpoint is calculated, i.e. before the current state is compared to previous state. Right now, there is no easy way to do it.
Solution 1 - step calculation:
Tool could print out number of steps ran and user then could just use "step number" and reach the new state.
Solution 2 - breakpoint at the end of program:
User then could just use "run" and reach the new state. Works for current method of fixpoint calculation.
Solution 3 - new command - stop before fixpoint calculation:
Easiest one to use for user, but may not be "easy as it seems" since the fixpoint calculation may not be straightforward.
The text was updated successfully, but these errors were encountered: