gopls/v0.7.4

Features

Editing support for Go template files

Gopls support for template files is now generally available. While editing files intended for use with the text/template or html/template packages, gopls can provide completion, syntax highlighting, jump-to-definition, find references, and diagnostics.

To use this feature, your editor or LSP client must be configured to activate gopls for Go template files. By default, gopls considers files ending with .tmpl or .gotmpl to be template files, though this is configurable via the templateExtensions setting. More information in the documentation.

Improved support for generic code when using the Go 1.18 beta

This release includes several bug fixes related to editing generic code, as well as many improvements to diagnostic precision when operating on type parameters. See the documentation for instructions on how to build gopls using a version of Go that supports generic code.

Fixes

A full list of all issues fixed can be found in the gopls/v0.7.4 milestone. To report a new problem, please file an issue at https://golang.org/issues/new.

Thank you to our contributors!

@guodongli-google @hyangah @jmesyou @pjweinbgo @ShoshinNikita @stamblerre @suzmue @timothy-king @zpavlinovic

gopls/v0.7.3

gopls/v0.7.3

Features

Exclude node_modules from the workspace by default

The directoryFilters setting now defaults to [-node_modules], since these directories never include Go code. This only applies to node_modules directories at the top level of the workspace, not arbitrary depths.

Detailed hover for runes

You will now see more information about the rune when you hover over it. For example:

Undeclared name suggested fix for functions

The undeclaredname analyzer now offers a suggested fix for undeclared function. Depending on the surrounding code, the suggested fix will either insert a new variable declaration (as before), or a new function declaration with inferred parameters and a body that panics. For example:

New analyzers for generic code (only with Go 1.18)

useany: Check for constraints that could be simplified to "any"
infertypeargs: Check for unnecessary type arguments in call expressions

Explicit type arguments may be omitted from call expressions if they can be
inferred from function arguments, or from other type arguments:

func f[T any](T) {}

func _() {
	f[string]("foo") // string could be inferred
}

Fixes

A full list of all issues fixed can be found in the gopls/v0.7.3 milestone. To report a new problem, please file a new issue at https://golang.org/issues/new.

Thank you to our contributors!

@chitoku-k @danp @rentziass @jhchabran @krobelus @marwan-at-work @leitzler

gopls/v0.7.2

gopls/v0.7.2

Fixes

A full list of all issues fixed can be found in the gopls/v0.7.2 milestone. To report a new problem, please file a new issue at https://golang.org/issues/new.

Thank you to our contributors!

@mdempsky @muirdm @NicholasAsimov @leitzler @ShoshinNikita @suzmue

gopls/v0.7.1

gopls/v0.7.1

Features

Experimental

Support go.work files (proposal)

In order to better support the new proposal for a multi-module workspace mode (golang/go#45713), gopls has added support for go.work files. Try adding a go.work file to the root of your module (you still need to enable experimentalWorkspaceModule mode) and try out the proposal!

Use invalid metadata

Set experimentalUseInvalidMetadata to true in your settings, and gopls will reuse outdated metadata until new package metadata has been successfully reloaded. This is useful if your go.mod file is temporarily invalid. In a future release, this setting will be moved out of experimental and deleted.

Fixes

A full list of all issues fixed can be found in the gopls/v0.7.1 milestone. To report a new problem, please file a new issue at https://golang.org/issues/new.

Thank you to our contributors!

@bcmills @dr2chase @dominikh @rentziass @GGCristo @jadekler Johnny Jacobs @KarthikNayak @marwan-at-work @muirdm @NicholasAsimov @OneOfOne @zyctree @leitzler @ShoshinNikita @danishprakash

gopls/v0.7.0

gopls/v0.7.0

Features

Postfix completions

Postfix completions are a new style of completions that can save you time by inserting more complex pieces of commonly-written code. All of the results end with !. This feature was added experimentally in gopls/v0.6.10 and is now enabled by default.

See this example:

New commands: List known packages and add import

These commands can be used to manually list available packages to import and then add an import to your file. They are currently not used by any known clients, but they will be made available through the Command Palette in VS Code in the next VS Code Go release.

Improvements

Memory usage

Improved trimming of the ASTs of dependency packages results in reduced memory usage, especially for projects with many dependencies. This may result in some hard-to-diagnose bugs that we're not yet aware of, so please report any surprising behavior via https://golang.org/issues/new.

Fixes

A full list of all issues fixed can be found in the gopls/v0.7.0 milestone. To report a new problem, please file a new issue at https://golang.org/issues/new.

Thank you to our contributors!

@muirdm @marwan-at-work @dominikh @leitzler @OneOfOne @zyctree @ShoshinNikita @KarthikNayak @suzmue @bcmills

gopls/v0.6.11

gopls/v0.6.11

This release contains mainly bug fixes. A full list of all issues fixed can be found in the gopls/v0.6.11 milestone. To report a new problem, please file a new issue at https://golang.org/issues/new.

Thank you to our contributors!

@ShoshinNikita @sakateka @muirdm Will Langford @empire @justplesh @suzmue

gopls/v0.6.10

gopls/v0.6.10

Features

t.Fatal snippet

If you trigger completion in a test function, on the line after a call to a function that returns an error, you will be offered a completion snippet for:

if err != nil {
    t.Fatal(err)
}

See the example below:

Experimental

Postfix completion snippets

Postfix completions are a new style of completions that can save you time by inserting more complex pieces of commonly-written code. All of the results end with !. Enable this feature by setting "ui.completion.experimentalPostfixCompletions": true.

See this example:

Fixes

A full list of all issues fixed can be found in the gopls/v0.6.10 milestone. To report a new problem, please file a new issue at https://golang.org/issues/new.

Thank you to our contributors!

@marwan-at-work @soluchok @zchee @ShoshinNikita @Makima0 @muirdm @steeve

gopls/v0.6.9

gopls/v0.6.9

This is a patch release to fix golang/go#45092.

gopls/v0.6.8

gopls/v0.6.8

This is a patch release to fix golang/go#45075.

gopls/v0.6.7

gopls/v0.6.7

Features

New analyzers

The unusedwrite and nilness analyzers are now available, but they are disabled by default. Note that enabling them permanently may significantly increase memory usage. You can configure analyzers through the analyses setting.

Improved hover with time.Duration

Hover for any constant of type time.Duration is shown both in nanoseconds and as a human-readable string.

Fixes

A full list of all issues fixed can be found in the gopls/v0.6.7 milestone. To report a new problem, please file a new issue at https://golang.org/issues/new.

Thank you to our contributors!

@findleyr @heschik @pjweinb @hyangah @ainar-g @glepnir @ShoshinNikita @msAlcantara