chore(deps): bump golang.org/x/tools from 0.17.0 to 0.35.0

[dependabot]

Bumps golang.org/x/tools from 0.17.0 to 0.35.0.

Release notes

Sourced from golang.org/x/tools's releases.

gopls/v0.19.1

This patch release changes the default value of the importsSource setting: v0.19.0 changed it from goimports to gopls; this release changes it back, due to a bug (#74280).

gopls/v0.19.0

Complete list of issues closed: gopls/v0.19.0 milestone

Configuration Changes

• The gopls check subcommand now accepts a -severity flag to set a minimum severity for the diagnostics it reports. By default, the minimum severity is "warning", so gopls check may report fewer diagnostics than before. Set -severity=hint to reproduce the previous behavior.

Navigation features

"Implementations" supports signature types (within same package)

The Implementations query reports the correspondence between abstract and concrete types and their methods based on their method sets. Now, it also reports the correspondence between function types, dynamic function calls, and function definitions, based on their signatures.

To use it, invoke an Implementations query on the func token of the definition of a named function, named method, or function literal. Gopls reports the set of function signature types that abstract this function, and the set of dynamic calls through values of such types.

Conversely, an Implementations query on the func token of a signature type, or on the ( paren of a dynamic function call, reports the set of concrete functions that the signature abstracts or that the call dispatches to.

Since a type may be both a function type and a named type with methods (for example, http.HandlerFunc), it may participate in both kinds of Implements queries (method-sets and function signatures). Queries using method-sets should be invoked on the type or method name, and queries using signatures should be invoked on a func or ( token.

Only the local (same-package) algorithm is currently supported. (https://go.dev/issue/56572 tracks the global algorithm.)

"Go to Implementation" reports interface-to-interface relations

The "Go to Implementation" operation now reports relationships between interfaces. Gopls now uses the concreteness of the query type to determine whether a query is "downwards" (from an interface to the types that implement it) or "upwards" (from a concrete type to the interfaces to which it may be assigned). So, for example:

• implementation(io.Reader) subinterfaces such as io.ReadCloser, and concrete implementations such as *os.File.

• implementation(os.File) includes only interfaces, such as io.Reader and io.ReadCloser.

To request an "upwards" query starting from an interface, for example to find the superinterfaces of io.ReadCloser, use the Type Hierarchy feature described below. (See microsoft/language-server-protocol#2037.)

Support for Type Hierarchy

Gopls now implements the three LSP methods related to the Type Hierarchy viewer: textDocument/prepareTypeHierarchy, typeHierarchy/supertypes, typeHierarchy/subtypes.

In VS Code, select "Show Type Hierarchy" from the context menu to see a tree widget displaying all the supertypes or subtypes of the selected named type.

... (truncated)

Commits

• 50ec2f1 go.mod: update golang.org/x dependencies
• 197c6c1 gopls/internal/mcp: more tuning of tools and prompts
• 9563af6 gopls/internal/mcp: include module paths in workspace summaries
• 88a4eb3 gopls/internal/cmd: wait for startup log in TestMCPCommandHTTP
• 4738c7c gopls/internal/cmd: avoid the use of channels in the sessions API
• ae18417 gopls/internal/filewatcher: skip test for unsupported OS
• 8391b17 gopls/doc: document Zed editor
• 778fe21 gopls/internal/util/tokeninternal: move from internal/tokeninternal
• 0343b70 internal/jsonrpc2/stack: move from internal/stack
• 8c9f4cc gopls/internal/filewatcher: refactor filewatcher to pass in handler func
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)