Go Modules Cheat Sheet

Post by eandre » Mon, May 03, 2021, 2:25 PM UTC

Post by Thaxll » Mon, May 03, 2021, 4:42 PM UTC

tomcam wrote: post #2

Ahhhh.... relief. The Go docs are vague on day-today tasks like this. Also how were those nifty arrows done?

Post by rainworld » Mon, May 03, 2021, 4:54 PM UTC

geodel wrote: post #4

Thaxll wrote: post #3

Earlier quoted context omitted.

vague? https://github.com/golang/go/wiki/Modules#daily-workflow

But I am millennial. I do not have time to read any document. There must be a way to just know about this or any other thing without ever learning about it.

  go get (-d) -u ./... && go mod tidy

Post by morelisp » Mon, May 03, 2021, 5:17 PM UTC

rainworld wrote: post #5

geodel wrote: post #4

Earlier quoted context omitted.

But I am millennial. I do not have time to read any document. There must be a way to just know about this or any other thing without ever learning about it.

Arguably updating packages could be a bit more obvious than go get (-d) -u ./... && go mod tidy

    go get -u

Post by whateveracct » Mon, May 03, 2021, 5:38 PM UTC

HumblyTossed wrote: post #8

Question: Why is go so integrated(?) with github? I mean, why can't I (or can I?) go get from my own personal gitlab server?