Codelens to debug benchmarks, ability specify output option for delve and bug fixes

New Features and Enhancements

• Teruo Kunihiro @1984weed

  • Configure the output option of delve in debug configuration.The location provided here is where delve will output the binary it then uses for debugging. PR 1564

• Harry Kalogirou @harkal

  • Codelens to debug benchmarks. PR 1566

• David Howden @dhowden

  • Show build errors at the right column in a line instead of showing them at the start of the line by using columns numbers returned from go build. PR 1573

• Ramya Rao (@ramya-rao-a)

  • Make links in test output clickable when it fails due to build errors. Feature Request 1562
  • Enable Go to Implementation to work both ways. Feature Request 1536

• Dan Mick @dmick

  • Include comments from struct definitions when showing the definitions on hover. PR 1559

• KataKonst @KataKonst

  • Use go vet instead of go tool vet from Go 1.10 onwards as the latter now supports all vet flags. PR 1576

• Luis GG @lggomez

  • Add option to never show the warning on editing generated files. PR 1537

• Jan Koehnlein @JanKoehnlein

  • Show warning when go binary is not found during build. PR 1543

Bug Fixes

• Kegsay @Kegsay

  • Fix bug where debug codelens would debug all tests that match the current test name. PR 1561

• Nuruddin Ashr (@uudashr)

  • Fix bug where internal packages are allowed to be imported when their path is substring of current package. PR 1535

• Ramya Rao (@ramya-rao-a)

  • Fix Go to Implementation feature when GOPATH is directly opened in VS Code. Bug 1545 and Bug 1554
  • Fix issue with debugging into std lib when remote debugging and remote path is a complete substring of the local path.

Fill struct fields with default values, show maps correctly when debugging and bug fixes

• Robin Bartholdson @buyology

  • New command Go: Fill Struct integrates the fillstruct tool that lets you fill struct fields with default values. PR 1506

• Ramya Rao (@ramya-rao-a)

  • Show key value pairs of map variables correctly in the variable pane when debugging. Fixes Bug 1384

• Nuruddin Ashr (@uudashr)

  • Fix the issue of various features not working with Go 1.10 due to regex failure on fetching the version. PR 1523

• Kevin Wiesmüller @kwiesmueller

  • Generating Unit Tests will not open a new editor for generated/updated test file if the file is already open and visible in another editor group. PR 1517

• Murad Korejo (@mkorejo)

  • Notify user when gopkgs fails to get packages that are needed to provide the completions for unimported packages. PR 1528

• Anatoly Milkov (@anatolym) and Christian Winther (@jippi)

  • Documentation Updates

More bug fixes

* [Bug 1449](https://github.com/Microsoft/vscode-go/issues/1449): Rename fails due to cgo not being able to find the go executable.  
* [Bug 1508](https://github.com/Microsoft/vscode-go/issues/1508): Broken Path in Windows when running Go tools

Bug fixes and Bug fixes

• Nikhil Raman (@cheesedosa)

  • Feature Request 1456: Show build/vet/lint status in status bar instead of opening output pane when run manually

• Ramya Rao (@ramya-rao-a)

  • Bug 1470: Go: Build Workspace command or the setting "go.buildOnSave": "workspace" results in persistent error from trying to build the root directory with no Go files.
  • Bug 1469: Formatting adds �� in Chinese files some times.
  • Bug 1481: Untitled files in empty workspace results in build errors
  • Bug 1483: Generating unit tests for a function generates tests for other functions with similar names

Bug fixes

• Ramya Rao (@ramya-rao-a)
  • Fix the issue that got introduced in the previous release, where formatter reverts changes unless goreturns is updated. Fixes Bug 1447
  • ~, $workspaceRoot and $workspaceFolder are now supported in the go.goroot setting
• Ben Wood @(benclarkwood)
  • Collapse single line imports into an import block when auto-completing symbols from unimported packages or when using the Go: Add Import command. Fixes Bug 374 with PR 500

Snippet descriptions in auto-completions, warning when trying to edit generated files and bug fixes

• Ramya Rao (@ramya-rao-a)

  • Setting go.inferGopath will now infer the correct GOPATH even in the below 2 cases which wasnt supported before
    • When a Go file is opened in VS Code directly without opening any workspace.
    • When GOPATH itself is directly opened in VS Code. Fixes Bug 1213
  • Use byte offset when calling gocode to fix issue with code completion when there are unicode characters in the file. Fixes Bug 1431
  • Add descriptions to the contributed snippets. These descriptions will appear in auto-completion and when using the Insert Snippet command
  • Fix "maxBufferExceeded" error by using spawn instead of exec when running formatters.
  • Use the new onDebugResolve activation event instead of onDebug to avoid activating the Go extension when other type of debug sessions are started

• halfcrazy

  • Fixed the upstream issue with goreturns: PR sqs/goreturns#42. This in turn fixes Bug 613 and Bug 630

• Nikhil Raman (@cheesedosa)

  • Show a warning when user edits a generated file. Feature Request 1295 via PR 1425

Snippet for methods on types in auto-completions, linting experience improvements and more

• Avihay Kain (@grooveygr)
  • Snippets for methods on types during auto-completion. Feature Request 168. PR 1368
• Matt Brandt (@Matt007)
  • Debug configuration snippet for remote debugging. PR 1365
• Ramya Rao (@ramya-rao-a)
  • Prompt to recompile dependent Go tools when GOROOT changes. Feature Request 1286
  • Support for ${workspaceFolder} in the below settings
    • go.gopath
    • go.toolsGopath
    • go.testEnvVars
    • go.testEnvFile
  • The Analysis Tools Missing message has bee updated to only appear for the tools backing basic features of the extension
  • Skip showing linting/vetting errors on a line that has build errors. Feature Request 600
  • Fix the issue of slow linters resulting in stale problem markers in updated file. Bug 1404
  • Deprecate go.formatOnSave setting in favor of editor.formatOnSave. To disable formatting on save, add the below setting:

    "[go]": {
        "editor.formatOnSave": false
    }
    

    This fixes the below issues
    • Cursor jumps unexpectedly when formatting on save. Bug 1346
    • Adopting the format on save feature of VS Code. Debt 540
    • Format-on-save messes up undo/redo stack Bug 678
    • FormatOnSave re-saves file Bug 1037
    • Save All doesnt format all files Bug 279
    • Slow format on save affects tests Bug 786

Build/vet/lint on demand, perf improvements, run benchmarks and more

• New commands

  • Frederik Ring (@m90)
    • Go: Run on Go Playground to run the current file (only if all its dependencies are from the std library) in the Go Playground using goplay. PR 1270. Feature Request #1211
      • Use the setting go.playground to control whether to run and/or share a link to the playground and/or open the playground in the browser.
  • Robin Bartholdson @buyology
    • Go: Benchmark Function At Cursor and Codelens for running benchmarks in test files. PR 1303. Feature Request #972
  • Andrew Nee (@ndrewnee)
    • Go: Lint Current Package and Go: Lint Workpsace to lint using the tool specified in the go.lintTool setting and the flags specified in the go.lintFlags setting. PR 1258. Feature Request #1041
  • Ramya Rao (@ramya-rao-a)
    • Go: Vet Current Package and Go: Vet Workpsace to vet using the flags specified in the go.vetFlags setting. Feature Request #1041
    • Go: Build Current Package and Go: Build Workpsace to build using the flags specified in the go.buildFlags setting and build tags specified in the setting go.buildTags. Feature Request #287
    • Go: Install Current Package to install the current package using the flags specified in the go.buildFlags setting and build tags specified in the setting go.buildTags. Feature Request #287

• Completion Improvements

  • wangkechun (@wangkechun)
    • Completions for standard packages are now shown before custom packages when providing completions for unimported packages. PR 1309
  • Ramya Rao (@ramya-rao-a)
    • gocode can now use gb specific rules when providing completions. Set the new setting go.gocodePackageLookupMode to gb to use this feature. Feature Request #547

• Performance improvements

  • Ramya Rao (@ramya-rao-a)
    • The autobuild feature of gocode which is known to slow completions is now disabled by default. Fixes Bug 1323
      • Since we use the -i flag when building, we do not rely on autobuild feature of gocode to ensure fresh results from dependencies.
      • If you have disabled the buildOnSave setting, then use the new Go: Build Current Package command once in a while to ensure the dependencies are up to date or enable the go.gocodeAutoBuild setting.
    • In Go 1.9 and higher, running the vet feature in the absence of vet flags will be faster due to the use of go vet ./... instead of go tool vet -flags. Fixes Bug 1215
    • Performance issues caused by a large number of lingering processes for vet/lint/hover features are now solved.
      • Measures are now in place to kill older processes before starting new ones for vet/lint feature. Fixes Bug 1265
      • For other features like hover/outline/definition etc. the cancellation token provided by the core is used to kill processes if the corresponding request from the core is cancelled. Fixes Bug 667

• Others

  • Phil Kates (@philk)
    • Fix the formatting issue due to stricter rules in the VS Code apis around configuration objects. PR 1334. Fixes Bug 1333.
  • David Marby (@DMarby)
    • Fix delve connection issues when verbose build flag is set. PR 1354
  • Jan Koehnlein @JanKoehnlein
    • Fix Open Workspace Settings action in the prompt to set GOPATH. PR 1375. Fixes Bug 1374
  • Ramya Rao (@ramya-rao-a)
    • Apply/Clear coverage in active editors of all editor groups rather than just the first one. Fixes Bug 1343
    • Fix the issue of codelens for references showing "0 references" when guru fails to provide references. Fixes Bug 1336
    • Support multiple buildtags in the go.buildTags setting. Fixes [Bug 1355]#1355).

Using latest debug apis from VS Code and bug fixes

• Nuruddin Ashr (@uudashr)

  • Do not show suggestions from internal packages of other projects. Fixes Bug 1256.

• Alexander Kohler (@alexkohler)

  • Fix issue with go.useCodeSnippetsOnFunctionSuggestWithoutType setting dropping parameters of same type. Fixes Bug 1279 via PR 1284
  • Remove duplciate compilation errors that can show up when entire workspace is built. Fixes Bug 1228 via PR 1269

• Paweł Słomka @slomek

  • Snippet for Example functions. PR 1281

• Ramya Rao (@ramya-rao-a)

  • Fix suggestions to import vendored packages in Windows. Fixes Bug 1147.
  • Fix extension activation issue in Windows when a Go file is opened without any folder open. Fixes Bug 1306
  • Use the newer debug APIs as the older ones will be deprecated in VS Code 1.18

Multi-root support, Improvements to auto-completions, running/debugging tests and more..

Multi Root support when using VS Code Insiders

We now have Multi Root support for Go. PR 1221 Please note:

• The settings at Folder level takes precedence over the ones at the Workspace level which in turn take precedence over the ones at the User level
• You can have the different roots in the multi-root mode use different GOPATHs. The experimental language server feature is not supported in such cases though.
• All current Go related features that refer to "workspace" will refer to the individual roots in the multi root mode. For example: Build/lint/vet/test workspace or Go to Symbol in workspace.
• Give it a try and log any issues that you find in the vscode-go repo

Auto-completion improvements

• Nuruddin Ashr (@uudashr)
  • Auto-completion for unimported packages that are newly installed/built will now show up without the need for reloading VS Code.
  • Completions from sub vendor packages that were showing up are ignored now. Fixes Bug 1251
  • The package snippet completion is now smarter when suggesting package names. PR 1220. It suggests
    • main when current file is main.go or there exists a main.go file in current folder
    • The folder name when the current file is internal_test.go
    • The folder name with _test when current file is a test file
    • If the folder name in above cases has - or ., then what appears after the - or . is suggested.
• Alexander Kohler (@alexkohler)
  • A new setting go.useCodeSnippetsOnFunctionSuggestWithoutType is introduced. This allows completions of functions with their parameter signature but without the parameter types. Feature Request 1241
• Miklós @kmikiy
  • 3 New snippets for the Log methods from the testing package

Improvements around running and debugging tests

• zhouhaibing089 (@zhouhaibing089)
  • Running and debugging tests for packages in symlinked folders is now possible. PR 1164
• Katsuma Ito (@ka2n)
  • The Debug Test codelens now uses the buildTags and buildFlags correctly. PR 1248
• Chase Adams (@chaseadamsio)
  • You can now run tests from unsaved files. Fixes Bug 1225
• Ramya Rao (@ramya-rao-a)
  • Changes done to coverage options and decorators in settings now apply immediately without the need for moving to another file and back. Fixes Bug 1171
  • The Run Test and Debug Test codelens react to change in the codelens setting immediately without the need for moving to another file and back. Fixes Bug 1172
  • $workspaceRoot will now be resolved when part of go.testEnvVars and go.toolsEnvVars setting.

Improvements around Packages

• Nuruddin Ashr (@uudashr)
  • Go: Browse Packages command will now include newly installed/built packages without the need for reloading VS Code.
• Hugo (@juicemia)
  • A new command Go: Get Package is introduced to run go get on the package in the import statement under the cursor. PR 1222