To be clear, this looks like a request for clearer Hover messages. Is that right?

@pjweinb I think I described it a bit more precise then that :) In summary just don't remove type const var func in the beginning of a hover message. Thank you

example2:

go doc http.HandlerFunc

package http // import "net/http"
type HandlerFunc func(ResponseWriter, *Request)
The HandlerFunc...
func (f HandlerFunc) ServeHTTP(w ResponseWriter, r *Request)

in hover message you get

HandlerFunc func(ResponseWriter, *Request)
http.HandlerFunc on pkg.go.dev
The HandlerFunc....

A person new to go thinks this
HandlerFunc = func(ResponseWriter, *Request)
so that means i can do this
HandlerFunc(ResponseWriter, *Request)
definitely a function because I read
...Func and func...

compiler error message haha wrong its a type

actually even worse you get

too many arguments to conversion to http.HandlerFunc: http.HandlerFunc("a", "b")

https://play.golang.org/p/NfpIDUr6teT

New go user ??? ok I am going to stick to js instead, go is waaaay to confusing

All I want to say is leaving out type makes a huge difference for new go developers

HandlerFunc func(ResponseWriter, *Request)

type HandlerFunc func(ResponseWriter, *Request)

I think the only case where a keyword is not present in the hover message is in the case of types, which is likely because of the way we format their hover. We can consider adding type to hover messages.

I tried hovering in Goland and the 'type' is displayed.
It seems to be the problem with vscode-go, not gopls.

@nasjp: Goland does not use gopls, so this is a gopls issue.

Change https://golang.org/cl/260006 mentions this issue: internal/lsp: add "type " to hover messages for structs/interfaces/etc