Thanks. If only the docs would make that clear.
My experience with reading them is: clear only if previously known. Much frustration about modules could have been avoided by more clearly written documentation So it goes -- rob drrob...@fastmail.com On Fri, Apr 9, 2021, at 11:01 AM, wagner riffel wrote: > On Wed, 7 Apr 2021 20:11:22 -0400 > rob <drrob...@fastmail.com> wrote: > > > Would it be a bad idea to use my ~go/src as a module? > > > > I don't think so, I do have one global module like this for my own toys > and throwaways programs. Yes, it would need to adjust your import paths > according to the module, when I migrated to module it was easier > because everything was inside the same global folder, so I just needed > to init a module with that name. > > > go mod tidy --> do I need this? > > > > go mod tidy adds missing modules in go.mod/go.sum that you're importing > from go sources, and removes dangling ones (not found in your go > sources but in your go.mod/go.sum), it's wise to run it if you're > initializing a module from an existing code base. > > --wagner > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/af7de826-b922-42d0-b471-ba2cf0ecda8e%40www.fastmail.com.
