panic: t.TypeName == nil

[idontneedgithub]

Trying to run golds on a project, this panic occurs:

Command: golds -theme=dark .

Output:

. . . . .
. . . . .
[Analyzing] Sorted packages by dependency relations: 165.083µs
[Analyzing] Collected source files: 467.473µs
[Analyzing] Collected declarations: 17.359748ms
panic: t.TypeName == nil

goroutine 29 [running]:
go101.org/golds/code.(*CodeAnalyzer).registerInstantiatedType(0xc004236008, 0xc025b1c840, {0xc0265f7ba0, 0x1, 0x1})
        /home/user/go/pkg/mod/go101.org/golds@v0.7.4/code/analyzer.go:346 +0x274
go101.org/golds/code.(*CodeAnalyzer).lookForAndRegisterUnnamedInterfaceAndStructTypes(0xc004236008, {0xb673d0?, 0xc014020060}, 0xc024aabe00)
        /home/user/go/pkg/mod/go101.org/golds@v0.7.4/code/analyzer.go:690 +0x358
go101.org/golds/code.(*CodeAnalyzer).analyzePackage_CollectDirectSelectors(0xc004236008, 0xc024aabe00)
        /home/user/go/pkg/mod/go101.org/golds@v0.7.4/code/code-analyse.go:2759 +0x5ab
go101.org/golds/code.(*CodeAnalyzer).AnalyzePackages(0xc004236008, 0xc024a71e58)
        /home/user/go/pkg/mod/go101.org/golds@v0.7.4/code/code-analyse.go:57 +0x1b9
go101.org/golds/internal/server.(*docServer).analyze(0xc000104380, {0xc0000242c0, 0x1, 0xc000139fb8?}, {{0xa6a64f, 0x6}, {0xc0000140a5, 0xb}, 0x0, 0x0, ...}, ...)
        /home/yser/go/pkg/mod/go101.org/golds@v0.7.4/internal/server/server.go:366 +0x45d
go101.org/golds/internal/server.Run.func1()
        /home/user/go/pkg/mod/go101.org/golds@v0.7.4/internal/server/server.go:139 +0xa7
created by go101.org/golds/internal/server.Run in goroutine 1
        /home/user/go/pkg/mod/go101.org/golds@v0.7.4/internal/server/server.go:138 +0x60e

[zigo101]

Thanks for the report.

Could you identify which type causes this panic? Or is your project open sourced?
Both are helpful for identifying this problem.

Otherwise, a version with more debug info outputs is needed.

Go custom generics bring much difficulties to this project (and many other Go tools).
Currently, I guess a generic type alias causes this panic, but I'm not very sure about it.

[zigo101]

@idontneedgithub I just released Golds v0.7.5. You can set the env var GoldsIssue52 with something when running golds to get more information of the type which causes the panic.