Billie Cleek

You're right; your initial approach won't work with the asynchronous nature it had. Changing `:GoImplements` to be a synchronous call is going to have performance problems in large repositories; if...

You're exactly right, and I have a local branch where I'm working on exactly this using a proof of concept that we worked out last year. It turns out that...

The code is in a stash on my local branch; it's not ready to be pushed any place yet.

`go.mod` isn't needed at all, because `go get` will do just fine in module mode.

vim-go purposefully builds the package of the current file and the `errors` package so that a build result file won't be produced. From http://golang.org/cmd/go: > When compiling multiple packages or...

That's not a decision that's up to vim-go. I agree that it would be optimal. Have you checked to see whether there's an issue for this on github.com/golang/go?

I experimented with using `go build -o /dev/null .` instead of `go build . errors`, but there was no performance improvement. Some further experimentation shows that the performance lag you're...

Given that there's a Go issue for this now, I'm going to leave this open so that we can track the linked Go issue and improve vim-go if/when the enhancement...

I have two questions for you to help me better understand the situation. 1. Should `15333 E184: No such user-defined command: Last` read `15333 E184: No such user-defined command: LastModified`?...

That's odd. The only command that vim-go sends to delve that has `Last` in it at all is https://github.com/fatih/vim-go/blob/d34c629b852cd4a308606791ca8a809cd8490886/autoload/go/debug.vim#L1605. Do you know what version of delve you have installed in...