Could Visual D remember expansion of debug watch variables?

[Rainer Schuetze]

On 24/10/2018 20:47, Michelle Long wrote:
> Sometimes I have a deep nesting of a variable that I have to expand many
> times to find some member to check the variable.
> 
> Each time I debug I have to spend about 30 seconds digging in to the
> variable in the watch window.
> 
> Could Visual D remember the previous run's expansion of variables and
> attempt to auto expand them when the next debug occurs? It would need to
> scroll to whatever variable was being viewed last too, and not just
> percent window in case new variables were added.
> 
> The idea is to sort of make it so that the watch window sorta of changes
> as little as possible between runs so no time has to be wasted each
> time. It's not so bad most of the time but in some cases it really adds
> to the time to debug.
> 

This is not under control of Visual D, but it is the Visual Studio
Debugger Environment that keeps track of the expansion state of locals
and watch expressions. AFAICT it doesn't change it if it can reconstruct
it while stepping or running to the next breakpoint, but collapses them
if an expression cannot be evaluated in between.