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 a = 3, and a won't update in the locals / watches that depend on a won't reevaluate. I'm not seeing a way for a debug adapter to work around this issue either, since afaik VS Code needs to send a variables request first in order to care about a variables response. VS Code needs to either handle stale expression reevaluation, or add something to the protocol where a debug adapter can notify VS Code that its variable state is stale.

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.
This issue is already captured in #2399 thus closing this as duplicate.

@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?

@ansyral thanks for pointing this out, I have pushed a fix which takes care of this issue cd79dfc