Questions left unanswered:
- When are go multi-module workspaces best used?
- What should you use for the module-path argument to `go mod init` if you don't ever intend to share the repo or you don't yet know where you will be sharing it?
- When are go multi-module workspaces best used?
- What should you use for the module-path argument to `go mod init` if you don't ever intend to share the repo or you don't yet know where you will be sharing it?
2. Anything is fine: just a name ("myproject"), a fake URL, a real URL. Whatever works for you.
This may seem overly simplistic and I'm not trying to be dismissive, but that's really what it comes down to. Sometimes things really are just simple.
I don't understand the desire to "standardize" and "document" everything to the microscopic detail.
- How to handle binary modules?