You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As being discussed in microsoft/vscode-go#2210, the feature of showing global variables when debugging requires calling ListPackageVars which is expensive in many cases. The setting showGlobalVariables was introduced for the very same reason of this feature being expensive.
This issue is to consider this setting to have the default value of false instead of true to improve the out of the box experience.
The text was updated successfully, but these errors were encountered:
stamblerre
changed the title
Show global variables when debugging should be disabled by default to improve perf
debug: disable showing global variables by default
Jun 3, 2020
@polinasok Since you are currently looking into the variables listing - what do you think about disabling this by default in the next release? The original issue had ~39 upvotes. I am leaning toward to accepting this.
I'd feel more comfortable if users can turn on/off the global variable listing on demand. Are you aware of any knobs that dynamically control the scope of variables in an active session?
There is no option currently to control this dynamically. We could create such an option, so variables are loaded only if the user expands the Global scope (which is like a made-up variable in the backend). It could be handled similarly to how we would autoload more variable data that was not loaded right away (this is already done for interfaces, but not other data in vscode-go).
As being discussed in microsoft/vscode-go#2210, the feature of showing global variables when debugging requires calling
ListPackageVars
which is expensive in many cases. The settingshowGlobalVariables
was introduced for the very same reason of this feature being expensive.This issue is to consider this setting to have the default value of
false
instead oftrue
to improve the out of the box experience.The text was updated successfully, but these errors were encountered: