Typecheck errors when calling a function in another go file in the same package. about vim-go

[aaronmcohen]

Completely agree. Complete goof on my part for the project location. That being said I have reproduced it in other locations such as ${GOPATH}/src.

So I deleted my existing .vim directory and did a fresh install of vim-go with no other plugins and it worked fine. The problem actually seems to come from the dense-analysis/ale plugin. I found dense-analysis/ale#4586 and let g:ale_go_golangci_lint_package=1 fixed it. Thank you @bhcleek for helping and I am closing this issue.

[lkramer]

Seeing the same thing after pulling the latest vim-go + GoUpdateBinaries in neovim

[bhcleek]

Why are you creating a module in $GOPATH/pkg? Does the problem you're seeing happen if you delete that directory?

cd ${GOPATH}/pkg
mkdir test
cd test
mod init test

Can you clarify what this means?

create a function in the main package outside the main.go file in the outside.go file

edit: figured out what you meant

[aaronmcohen]

@bhcleek Yeah this originally happened in another coding project which worked great prior to upgrading vim-go. Those instructions were to just build a simple reproducible test case. Clearing out my entire ${GOPATH} does not solve the issue. Also the same steps will fail in the ${GOPATH}/src directory.

Out of curiosity are you seeing the same behavior in your coding projects?

[bhcleek]

I'm not seeing this at all. What operation did you execute to cause the error?

[aaronmcohen]

oddly enough it was just PlugUpdate & GoUpdateBinaries

[aaronmcohen]

What kind of debug information can I provide which will better provide insight to the issue?

[bhcleek]

Just for clarity as an aside; Go source code should not be placed in $GOPATH/pkg. The pkg directory is intended for Go to use for a variety of its internal uses. If you're able to duplicate your issue without explicitly creating any source code files in that directory, then it's unlikely to be a cause of the problem you're seeing. But I'd advise against it as a general practice anyway.

[bhcleek]

oddly enough it was just PlugUpdate & GoUpdateBinaries

What other plugins were updated with PlugUpdate?

Can you duplicate this problem when vim-go is the only plugin?

Also, vim-go isn't going to perform any operations that would cause errors to be displayed like that unless you did something. Think of it from my perspective: I don't see any vim commands or keystrokes being described here, only the creation of a file. Clearly there's some missing steps for me to be able to duplicate what you're doing.

edit: fixed a typo