A repository contains one or more modules. A module is a collection
of related Go packages that are released together. A Go repository typically
contains only one module, located at the root of the repository. A file named
go.mod there declares the module path : the import path
prefix for all packages within the module. The module contains the packages in
the directory containing its go.mod file as well as subdirectories
of that directory, up to the next subdirectory containing another
go.mod file (if any).
Note that you don't need to publish your code to a remote repository before you
can build it. A module can be defined locally without belonging to a repository.
However, it's a good habit to organize your code as if you will publish it
someday.
Each module's path not only serves as an import path prefix for its packages,
but also indicates where the go command should look to download it.
For example, in order to download the module golang.org/x/tools,
the go command would consult the repository indicated by
https://golang.org/x/tools (described more here).
An import path is a string used to import a package. A package's
import path is its module path joined with its subdirectory within the module.
For example, the module github.com/google/go-cmp contains a package
in the directory cmp/. That package's import path is
github.com/google/go-cmp/cmp. Packages in the standard library do
not have a module path prefix.
If you want to change selection, open document below and click on "Move attachment"
How to Write Go Code - The Go Programming Languageurce files in the same directory that are compiled together. Functions, types, variables, and constants defined in one source file are visible to all other source files within the same package. <span>A repository contains one or more modules. A module is a collection of related Go packages that are released together. A Go repository typically contains only one module, located at the root of the repository. A file named go.mod there declares the module path: the import path prefix for all packages within the module. The module contains the packages in the directory containing its go.mod file as well as subdirectories of that directory, up to the next subdirectory containing another go.mod file (if any). Note that you don't need to publish your code to a remote repository before you can build it. A module can be defined locally without belonging to a repository. However, it's a good habit to organize your code as if you will publish it someday. Each module's path not only serves as an import path prefix for its packages, but also indicates where the go command should look to download it. For example, in order to download the module golang.org/x/tools, the go command would consult the repository indicated by https://golang.org/x/tools (described more here). An import path is a string used to import a package. A package's import path is its module path joined with its subdirectory within the module. For example, the module github.com/google/go-cmp contains a package in the directory cmp/. That package's import path is github.com/google/go-cmp/cmp. Packages in the standard library do not have a module path prefix. Your first program To compile and run a simple program, first choose a module path (we'll use example/user/hello) and create a go.mod file that declares it: $ mkdir hello # Alternativel Summary
| status | not read | | reprioritisations | |
|---|
| last reprioritisation on | | | suggested re-reading day | |
|---|
| started reading on | | | finished reading on | |
|---|
Details