Well, my embarrassingly incorrect assumption came about from a package I was writing recently; I was using the go mod tool to initialize my go.mod rather than writing the file myself, and as an import statement I first tried using the local filepath, which of coarse didn't work. Then I tried things like: "." (yielding error: unknown import path "_/home/k/code/go/delete": internal error: module loader did not resolve import" upon build (but it let me initialize the module without issue). What finally did work, was when I used a GitHub repo URL that I created only for this purpose, which is what ultimately brought about my assumption. It never occurred to me to use a fictitious import path because, well, there is nothing there.
So it was my mistake (*egg on my face ¯\_(ツ)_/¯) But thx for the replies. -K -- 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 golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
