Bit of a strange one... I created a new module this morning, and just renamed the directory, module and associated package (all the same). I have a sub module (package main) that references the parent module, but we are talking about a dozen lines of code in the whole project so far. So 'go build' complains 'cannot load <oldname>: cannot find module providing package <old name>'
So I was thinking something must be cached. I deleted a go.sum file, since there were some strange entries in it. And I also tried the following: 'go clean -modcache' and 'go clean -cache' but they both return the same error. I remembered reading about cached files in go/pkg/mod/cache and I found a recent timestamped .info file in vcs that references git2:<old name> Interesting because I'm not using git so far since it's a new folder/project. So I deleted this file, the .lock and associated folder. 'go build' however still fails with the same error, and also recreates these strange vcs entries still with the old name. I can't see any hidden files in the project directories, and I cant find any references anywhere else to the old name. Any tips for other caches where it might be pulling this information from please? macos 10.12.4, go 1.12 -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
