Go Keyword import

External

• https://golang.org/ref/spec#Import_declarations

Internal

• Lexical Structure
• Packages

Overview

An import declaration states that the current package depends on the functionality of the imported package and wants access to its name space. Thus, the current package gains access to the exported identifiers exposed by the imported package.

...
import [package-name-alias] "package-path-string-literal"
...

Example

...
import "net/http"
import "project1/blue"
...

The package path is enclosed in double quotes. It is a string literal. It is NOT the package name, but it helps the compiler to locate the package, instead.

The package path represents a local file system path fragment. That path fragment is supposed to live under a src directory whose parent is listed in the GOPATH environment variable. Note that if the package path has multiple segments, only the last one represents the package name and can used to prefix identifiers belonging to the imported package, in the program. For example, if we import import "project1/blue", we only use blue to qualify identifiers from that package: blue.DoSomethingBlue()

The package-name-alias is optional, and it should be used when we have a package name conflict - we're trying to use two package whose terminal path segment is the same. If package-name-alias is not specified, the package will be referred as the last segment of the path.

Importing Multiple Packages

import (
    "fmt"
    "strings"
)

Accessing an Identifier from an Imported Package

Once a package has been declared as "imported", all exported identifiers from the imported package are available in the importing package. In order to access an individual exported identifier, the identifier should be prefixed with the name of the package. For example, in order to access the struct Box exposed by package "pkgA", we do this:

import "pkgA"
...
func f() {
    ...
    var b pkgA.Box
    ...
}

How Packages are Resolved

The algorithm is described here:

GOPATH