-
Notifications
You must be signed in to change notification settings - Fork 645
Allow changing showGlobalVariables in settings #2323
Comments
@aschade92 The
Can you point us to some docs or discussion around this? |
Cool yeah that worked for me. Is there any way to apply this settings in the workspace settings so that it can be used for running tests? (ie pressing the test or debug button above a test?)
Here are a couple that discuss this issue but I don't think that's super important for the purposes of the thread anymore: |
I'd be also interested in a way to disable the global variables when using the "Debug test" code lens. |
Not at the moment, but we should be able to enable add it to the PRs are welcome to do this
|
@ramya-rao-a easy enough, I made a PR for this one |
In the latest beta version (0.9.3-beta.2) of this extension, |
This feature is out in the latest release(0.10.0) of the Go extension |
If I'm using the extension version
0.8.1-beta.7
debugging is very fast and onlylocal
appears in the variable window:config:
Now if I install
0.8.1-beta.12
or0.9.1
, debugging is slightly to significantly slower depending on the amount of variables that are getting collected by the debugger. SettingshowGlobalVariables
to false (as mentioned here: #2133 (comment)) doesn't really seem to do anything for me (there might be a slight improvement but there is noticeable lag here that is not present in the beta version0.8.1-beta.7
I mentioned above). Regardless of whether or notshowGlobalVariables
is set tofalse
,global
still appears in the frame:I'm guessing that there is still some other processing being done here in the latest versions that wasn't being done in versions where the debugger works much more fluidly. Is there a way to just completely disable global variables? Is this even expected when
showGlobalVariables
is set totrue
? Global variables aren't really recommended in general by the go community anyways so an option to disable them completely in favor of higher performance would be appreciated.Steps to Reproduce:
The text was updated successfully, but these errors were encountered: