Still having some difficulties with Google Go tagging in SE 22.0.1.

[asandler]

There is clearly an improvement compared to 22.0.0.9, however I am still having some problems.
We have large package called "tables". This package spans multiple files and mostly has definitions of structures and functions that operate on these structures. For some reason SE does not understand this package and its contents. Typing something like "tables." does not produce list of possible completions, like it would with other packages. The package is imported via directory it lives in - it is in directory called "ivy-tables", so we import "ivy-tables".
I tried to reproduce this problem with a scaled down demo version of the project and it does not reproduce. It has to be something in our project that causes this. How I go about and debug something like this?

Thanks,
Merry Christmas.

[Clark]

You could try rebuilding your tag file (Project>Retag Workspace).

[asandler]

I tried that, one of the first things I tried. Unfortunately it did not help.
Anything else I can do?

[patrick]

Could you send us the scaled down demo anyway, even if it doesn't reproduce the problem?  It would probably save us a lot of questions about the structure that will come up as we look at your tag file.

Edit:  also, lets us know how your GOPATH is set relative to this project - for example GOPATH is /home/something/goproject, and the demo is at /home/something/goproject/src/demo.   We were looking at some test projects and your tag file, and have a sneaking suspicion that where the project is relative to the GOPATH plays a part in the problem.

[asandler]

FWIW attached.
I tried to play with the case when there are multiple files in a library and file names, package name and directory name are all different. As I said it worked.

[patrick]

Thanks, not a problem if it doesn't reproduce with this one, this is more for our reference so we can be confident the project structure is correctly reflected in the tag file.

In the tag file you sent, we can see the tables package in the tag file, and a bunch of symbols in that package that should show up for completion, but we're still trying to work out why the lookup fails to find them. 

[asandler]

I think I reproduced the problem.

I noticed couple of more anomalies:
1. We often define a bunch of types using following syntax:

Code: [Select]

type (
    TypeA uint64
    TypeB uint64
)Looking at Defs window, these types appear as uint64, not as TypeA or TypeB.
2. We have large number of structure methods. Method names are the same. Structure is different every time. Defs window shows method names correctly, but does not reflect structure name in any way.

I copied small part of our code to my dummy project to src/ivy-tables/file1.go. The code itself is kind of useless because I had to rename/remove a bunch of external dependencies. However it does have two peculiarities above.
If you look at main in src/dir1/dir1.go, try entering "tables.", SE does not offer any completion options for me. Defs window in file1.go shows same two problems as in my main project.

[patrick]

That's great, we can reproduce both problems with that project.  Thanks.

[Dennis]

These issues will be fixed in the next release.

[asandler]

Thanks. Just to confirm, next release means 22.0.2 and not one of the hot-fixes, right?

[Dennis]

Unfortunately, the problem can not be hot-fixed.