Evaluator produces confusing locals view while debugging #1436
Assignees
Labels
bug
Something isn't working
Comments
swernli
added a commit
that referenced
this issue
Apr 29, 2024
This adds new execution graph nodes for pushing and popping variable scopes that are used only while debugging (like statement nodes) so that the evaluator can correctly respond to local variable requests during debugging. Fixes #1436
github-merge-queue bot
pushed a commit
that referenced
this issue
Apr 29, 2024
This adds new execution graph nodes for pushing and popping variable scopes that are used only while debugging (like statement nodes) so that the evaluator can correctly respond to local variable requests during debugging. Fixes #1436
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The evaluator refactoring in #1261 had an unexpected side effect of leaving variables in scope too long, which can cause confusing debugger output:
The
y: 1entry should only be visible while inside the block for the if-expression. The control flow graph will need to be updated to include scope entry and exit markers when running in debug mode.The text was updated successfully, but these errors were encountered: