[x/programs] program recursion test #910
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
By curiosity, I wanted to write a recursion test just to make sure that unwinding works as expected and that the execution will run out of units.
This is still a WIP because although this property is verified, there is no way to assert that an execution failed. Additionally, there is an error log message from the simulator saying that the execution ran out of units which is annoying to have on the terminal.
I think that it is blocked by #865, #595, and the fact that the logging is printed on stderr because of the communication pattern.
Closes #899
edit: there is also this deserialization error which was not caught. I'm wondering if we could tune the static analysis to detect those blunders.