You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The algorithm for deducing which version of the Go spec applies to a given Go source file, and which GODEBUG and GOEXPERIMENT flags are in force, is unfortunately rather complicated. Gopls could help by adding to the Hover result for the package declaration an explanation of which Go version is in force and why, and the values of any non-default GODEBUG and/or GOEXPERIMENT settings. (Other UI approaches are possible.)
The text was updated successfully, but these errors were encountered:
gopherbot
added
Tools
This label describes issues relating to any tools in the x/tools repository.
gopls
Issues related to the Go language server, gopls.
labels
Aug 15, 2024
When hovering over a package name in a package declaration, show
language version and GODEBUG values that differ from the toolchain
default. Also, for consistency with other hover content, show the
package declaration as the 'signature' of both a package name and an
import.
Finally, to help differentiate this information, introduce hlines in
the hover output between logical sections. This is similar to what is
done by other LSP servers such as tsserver.
Fixesgolang/go#68900
Change-Id: I5013bb9fb4086c71cc3565fd67993764cad69237
Reviewed-on: https://go-review.googlesource.com/c/tools/+/626276
Reviewed-by: Alan Donovan <[email protected]>
Auto-Submit: Robert Findley <[email protected]>
LUCI-TryBot-Result: Go LUCI <[email protected]>
The algorithm for deducing which version of the Go spec applies to a given Go source file, and which GODEBUG and GOEXPERIMENT flags are in force, is unfortunately rather complicated. Gopls could help by adding to the Hover result for the package declaration an explanation of which Go version is in force and why, and the values of any non-default GODEBUG and/or GOEXPERIMENT settings. (Other UI approaches are possible.)
The text was updated successfully, but these errors were encountered: