-
```
godef optimistically assumes that it can deduce the package
identifier from the import path. This is often, but not
always the case. It should actually import the package
in question, although thi…
-
```
godef optimistically assumes that it can deduce the package
identifier from the import path. This is often, but not
always the case. It should actually import the package
in question, although thi…
-
```
godef optimistically assumes that it can deduce the package
identifier from the import path. This is often, but not
always the case. It should actually import the package
in question, although thi…
-
```
godef optimistically assumes that it can deduce the package
identifier from the import path. This is often, but not
always the case. It should actually import the package
in question, although thi…
-
i'm new to Go and GoClipse and i'm not able to compile a simple "hello World" on my linux machine. Here is my configuration:
- Eclipse Mars.2
- GoClipse 0.16.1
On Windows->Preferences->Go:
…
-
## Reproduction steps: ##
1. Install go version 1.16+ or export GO111MODULE=on
2. Go to the module directory of a module that does not include a go.mod file--for example, confluentinc's kafka client…
-
I have Go installed to a non-standard path. With Go 1.9 all you need is the `go` executable on the path and then Go figures everything out from there. However `godef` is not so clever and wants `GOROO…
-
In real vim, after install plugin vim-go and set shotcut for :GoDef to "gd", shotcut ":GoDefPop" to "Ctrl-t", when press "gd" in some function, you can jump to its definition, then you can just press…
-
I have a utility that retrieves a list of mountpoints, and checks their disk usage. I can compile on Windows, Linux, FreeBSD (x86). I can even compile linux + arm64, but not FreeBSd. I would like to g…
-
Seems a lot of tools use godef to do resolution of their symbols when jumping to sources. With vgo's support for multiple versions in `$GOPATH/src/v` this seems like something godef could really help …