-
Notifications
You must be signed in to change notification settings - Fork 27.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SetVariable doesn't trigger reevaluation of stale variables #8118
Comments
June to investigate |
In general, this issue can be expanded to evaluating any expression. I hadn't even thought of the repl in the debug console, but you can trigger expressions such as |
Ok I have pushed a fix that the watch expression are always up to date (when evaluting from repl or changing variable values). Now we have the issue that the local variables can be outaded if an evaluation happens in the repl, or if a variable that is dependent upon is changed via setVariable. @wesrupert @weinand please comment on that issue with ideas on how to update variables after evaluation. VSCode can send the variables request again (but that seems to heavy to be done on each repl evaluation) - or the adapter could somehow notify vscode that a variables inside locals has updated. I am open for suggestions |
@isidorn seems right now the code to trigger an event to re-evaluate expressions in watch window is removed. See setVariable. And if I set a variable, its value in watch window is still out of sync. Any idea about this? |
Assigning to a variable doesn't prompt a reevaluation of any variables that depend on it. Variables can be stale after setting a variable in languages such as C# (e.g. a property in the locals window), and watch expressions can be stale in all languages since they can be arbitrary expressions dependent on the changed variable.
The text was updated successfully, but these errors were encountered: