You are right. Thanks for the correction. Import path is the correct Go
term.
On Monday, May 25, 2020 at 12:04:16 PM UTC+7, Jan Mercl wrote:
>
> On Sun, May 24, 2020 at 6:58 AM Henry >
> wrote:
> > To create a Go Module, step inside your project folder, and type go mod
> init where is the qu
On Sun, May 24, 2020 at 6:58 AM Henry wrote:
> To create a Go Module, step inside your project folder, and type go mod init
> where is the qualified name of your project. For
> instance, if you want to call your project "github.com/henry/myproject", then
> inside your myproject folder, type g
Here is a brief tutorial for those new to Go Module. This is by no means a
comprehensive guide to Go Module, but I hope this should be enough to get
you started.
What is Go Module, and why you should be using one? Go Module is a
dependency management tool. The primary benefit of Go Module is th
I would work through
https://golang.org/doc/code.html
- Amnon
On Friday, 22 May 2020 12:59:03 UTC+1, lj0...@gmail.com wrote:
>
> It looks like I am not only one to struggle with (new?) go modules.
> I still consider me as novice to GO but the major problem is as usual, the
> focus.
>
> 1. Mod
It looks like I am not only one to struggle with (new?) go modules.
I still consider me as novice to GO but the major problem is as usual, the
focus.
1. Modules are complicated to understand
2. Lack of examples (of real use, not just POC)
3. Focus on extra (scale up) details (that are surely im
Interesting. At first sight this should work.
You definitely don't need a go.mod file in ~HOME/src/myrepo/cmd/cmd1
Which go version are you running?
What is your $GOPATH set to?
What output does cd ~HOME/src/myrepo; go build give?
The usual convention is to push the code in a VCS such as githu
