Billie Cleek

It looks like it's a matter of setting `GOROOT` and maybe `GOFLAGS` correctly when Vim is started, and maybe using `:GoBuildTags` afterwards: https://github.com/pcolladosoto/tinygo.nvim/blob/main/lua/tinygo/init.lua. I don't know that there's anything to...

Thank you, @findleyr; I appreciate the fast turnaround. I'll work to refactor vim-go to use `FullDocumentation`.

That's interesting. Strangely, there are no syntax highlighting problems if this is done without using a `var` or `const` block.

Note that in general your two examples show that the syntax highlighting provided by vim-go is working in general. The problem you're experiencing seems to be related to diagnostics by...

I don't think it's actually an issue with `gopls`; I suspect it's an issue with your code that `gopls` identifies for you. Can you: 1. add `let g:go_debug=['lsp']` to your...

I'm not sure what's going on yet. Clearly, `gopls` provides the diagnostics in both cases. There's nothing about vim-go that varies highlighting behaviors based on the version listed in the...

@albdewilde did you find an answer to this? I suspect the problem was related to a build constraint or a `go` directive in a dependency...

Yes, it was removed when vim-go dropped guru support. It may be possible to bring it back with a refactor to rely on gopls instead, though. I'll look into it.

@Pokom you're right; the tutorial needs to be updated. It's mostly correct, but the implementation details have changed somewhat.

Have you rebuilt `gopls` with `:GoUpdateBinaries gopls` since you updated your system's version of Go to 1.23?