Go Modules vs Package

Question

just starting to learn about Go Modules. I have a question on importing local packages inside the same module. The example I am looking at is this repo:

https://github.com/Azure/azure-service-bus-go

The module is module github.com/Azure/azure-service-bus-go. There is a separate package inside that module, atom (but it's not a module itself). When files inside the main package import atom, they do it like this: import "github.com/Azure/azure-service-bus-go/atom" -- see queue_manager.go as an example.

What I do not quite understand -- how does GO know to look at the local atom package, as opposed to, say the one on Github? It seems confusing to me that something that is part of the module being modified is referenced by a remote/absolute URI. Is it guaranteed that if I modify the file on local disk and build I'm actually referencing the latest version as opposed to something already pushed?

As a toy exercise I tried to create a module with a non-existent Github URI and it did in fact appear that go mod tidy tried to look that up against Github, even though a local copy did in fact exist

Answer 1

The module directive in the go.mod file declares the import-path prefix for all of the packages within that module.

If you are just starting to learn about Go modules, the Create a Go module tutorial might be a good place to start.

Answer 2

• A module is a collection of go packages.
• A package is a directory of .go files. Using packages, you organize your code into reusable units.
• We can add a module to go project or upgrade the module version.