[release] prepare v0.35.2 release

073136db3 CHANGELOG.md: update for v0.35.2
8e5969fe0 src/goToolsInformation: pick up gopls release
55683f5fd src/goToolsInformation: update hardcoded gopls version
886decb92 tools: generate inlay hints settings from gopls settings
7467f2672 README: edit Quickstart and Features section for clarity
e4a94d253 .github/workflows: fix wiki.yml
84fe4e7da .github/workflows: add go1.19rc2 to long/smoke tests
d11476774 commands: add go.goroot command
484a3ba45 test/gopls/vulncheck: add logging for viewer test failure
5bf723727 test/integration/extension: disable all "Test Completion Snippets *"
f4fcd7ad6 test/integration/goDebug: make invalid flag test faster
cbecbf8a2 test/integration/goExplorer: fix 'env tree items' test
e91d0e84f test/integration/install: stub languageserver restart command
a6729ef68 test/integration/goDebug: speed up setUpRemoteProgram
78c2fac41 Revert "src/goInstallTools: show error if go.languageserver.restart fails"
aa3de7f87 test/integration: catch failed await in lint test
b90e57e68 .vscode/launch.json: remove outFiles and deprecated attributes
d2afd7d70 src/goTest/resolve: fix nested packageDisplayMode handling on win32
47f6dfae8 test/integration/goTest: fix populateModulePathCache
1adebbbee test/integration/goTest.run: increase discover&run timeout
ffae00196 test/integration/goDebug: skip redundant tests in withConsole mode
c90973864 test/integration/goDebug: skip legacy da testing on windows
a39ef240a package.json: remove tslint
1dfac1444 .github/workflows: drop 1.15 from long test
944b1d477 .github/workflows: remove 'stable' unnecessary in setup-go@v3
21bbd7be8 test: skip flaky debug test
305bea73a .github/workflows: upgrade setup-go to v3 and enable caching
b6aad3e65 .github/workflows: upgrade checkout/node workflows to v3
9bb57d8ac test/integration: skip tests broken on windows
b012df443 src/goInstallTools: show error if go.languageserver.restart fails
c8598b13c test/integration/goDebug: catch any error while cleaning up
8f6cb5dee goGenerateTests: resolve config file path
aba30790d CHANGELOG.md: add v0.35.1 description
bfdb91c89 package.json: update dev version
4bd0f3323 docs/debugging.md: fix missing "" in example

Change-Id: I7504ae5e6d9c40009ad0feb6317f7f1000987012
tree: 925fee911528b5add556ebc1db22a801e77da306
  1. .github/
  2. .vscode/
  3. build/
  4. docs/
  5. languages/
  6. media/
  7. snippets/
  8. src/
  9. syntaxes/
  10. test/
  11. third_party/
  12. tools/
  13. typings/
  14. .editorconfig
  15. .eslintignore
  16. .eslintrc.json
  17. .gitignore
  18. .prettierrc.js
  19. .prettierrc.json
  20. .vscodeignore
  21. CHANGELOG.md
  23. codereview.cfg
  24. go.mod
  25. go.sum
  27. package-lock.json
  28. package.json
  29. README.md
  30. SECURITY.md
  31. tsconfig.json

Go for Visual Studio Code


The VS Code Go extension provides rich language support for the Go programming language.

📣 Remote attach debugging is now available via Delve's native DAP implementation with Delve v1.7.3 or newer. It enchances remote debugging with the same debugging features that are already in use for local debugging. It is now the default with the Go Nightly build of the extension and will become the default for the stable releases in mid 2022. We recommend switching your remote attach configurations in launch.json to use "debugAdapter":"dlv-dap" now to verify that this works for you. Please file a new issue if you encounter any problems.

📣📣 Watch Debugging Treasure Hunt from GopherCon 2021 for a fun take on a debugging demo with VS Code Go and Delve DAP.

Quick Start

Welcome! 👋🏻
Whether you are new to Go or an experienced Go developer, we hope this extension fits your needs and enhances your development experience.

  1. Install Go 1.14 or newer if you haven't already.

  2. Install the VS Code Go extension.

  3. Open any directory or workspace containing Go code to automatically activate the extension. The Go status bar appears in the bottom left corner of the window and displays your Go version.

  4. The extension depends on go, gopls, dlv and other optional tools. If any of the dependencies are missing, the ⚠️ Analysis Tools Missing warning is displayed. Click on the warning to download dependencies.

    See the tools documentation for a complete list of tools the extension depends on.

You are ready to Go :-)    🎉🎉🎉

What's next

If you are new to Go, this article provides the overview on Go code organization and basic go commands. Watch “Getting started with VS Code Go” for an explanation of how to build your first Go application using VS Code Go.

Feature highlights

  • IntelliSense - Results appear for symbols as you type.
  • Code navigation - Jump to or peek at a symbol's declaration.
  • Code editing - Support for saved snippets, formatting and code organization, and automatic organization of imports.
  • Diagnostics - Build, vet, and lint errors shown as you type or on save.
  • Enhanced support for testing and debugging

See the full feature breakdown for more details.

In addition to integrated editing features, the extension provides several commands for working with Go files. You can access any of these by opening the Command Palette (Ctrl+Shift+P on Linux/Windows and Cmd+Shift+P on Mac), and then typing in the command name. See the full list of commands provided by this extension.

⚠️ Note: the default syntax highlighting for Go files is provided by a TextMate rule embedded in VS Code, not by this extension.

For better syntax highlighting, we recommend enabling semantic highlighting by turning on Gopls' ui.semanticTokens setting. "gopls": { "ui.semanticTokens": true }


The extension uses a few command-line tools developed by the Go community. In particular, go, gopls, and dlv must be installed for this extension to work correctly. See the tools documentation for a complete list of tools the extension depends on.

In order to locate these command-line tools, the extension searches GOPATH/bin and directories specified in the PATH environment variable (or Path on Windows) with which the VS Code process has started. If the tools are not found, the extension will prompt you to install the missing tools and show the “⚠️ Analysis Tools Missing” warning in the bottom right corner. Please install them by responding to the warning notification, or by manually running the Go: Install/Update Tools command.

Setting up your workspace

Go modules are how Go manages dependencies in recent versions of Go. Modules replace the GOPATH-based approach to specifying which source files are used in a given build, and they are the default build mode in go1.16+. While this extension continues to support both Go modules and GOPATH modes, we highly recommend Go development in module mode. If you are working on existing projects, please consider migrating to modules.

Unlike the traditional GOPATH mode, module mode does not require the workspace to be located under GOPATH nor to use a specific structure. A module is defined by a directory tree of Go source files with a go.mod file in the tree's root directory.

Your project may involve one or more modules. If you are working with multiple modules or uncommon project layouts, you will need to configure your workspace by using Workspace Folders. Please see this documentation about supported workspace layouts.


The extension needs no configuration and should work out of the box. However, you may wish to adjust settings to customize its behavior. Please see the settings documentation for a comprehensive list of settings. See advanced topics for further customizations and unique use cases.


If the extension isn't working as you expect, you can take a look at our troubleshooting guides. There is one for general troubleshooting, and another specifically for troubleshooting the debugging feature.

Ask for help

If the troubleshooting guides did not resolve the issue, please reach out to us by filing an issue, starting a GitHub discussion, or by asking a question on Stack Overflow.

Also, you can take a look at go.dev/learn and golang.org/help for more general guidance on using Go.

Preview version

If you'd like to get early access to new features and bug fixes, you can use the nightly build of this extension. Learn how to install it in by reading the Go Nightly documentation.


We welcome your contributions and thank you for working to improve the Go development experience in VS Code. If you would like to help work on the VS Code Go extension, please see our contribution guide. It explains how to build and run the extension locally, and describes the process of sending a contribution.

Code of Conduct

This project follows the Go Community Code of Conduct. If you encounter a conduct-related issue, please mail conduct@golang.org.