Go (programming language) - Wikipedia https://en.wikipedia.

org/wiki/Go_(programming_language)

Go (programming language)
(Redirected from Golang)

Go is a statically typed, compiled high-level programming

Go
language designed at Google[13] by Robert Griesemer, Rob Pike,
and Ken ompson.[4] It is syntactically similar to C, but also
has memory safety, garbage collection, structural typing,[8] and
CSP-style concurrency.[14] It is oen referred to as Golang
because of its former domain name, golang.org, but its
Paradigm Multi-
proper name is Go.[15]
paradigm:
ere are two major implementations: concurrent
imperative,
▪ Google's self-hosting[16] "gc" compiler toolchain, functional[1]
targeting multiple operating systems and object-
WebAssembly.[17] oriented[2][3]

▪ gofrontend, a frontend to other compilers, with the Designed by Robert

libgo library. With GCC the combination is gccgo;[18] Griesemer
Rob Pike
with LLVM the combination is gollvm.[19][a]
Ken
A third-party source-to-source compiler, GopherJS,[21] compiles Thompson[4]
Go to JavaScript for front-end web development.
Developer The Go
Authors[5]
History First appeared November 10,
Go was designed at Google in 2007 to improve programming 2009
productivity in an era of multicore, networked machines and Stable release 1.22.2[6] / 3
large codebases.[22] e designers wanted to address criticisms April 2024
of other languages in use at Google, but keep their useful
Typing Inferred, static,
characteristics:[23]
discipline strong,[7]
structural,[8][9]
▪ Static typing and run-time efficiency (like C)
nominal
▪ Readability and usability (like Python)[24]
Memory Garbage
▪ High-performance networking and multiprocessing management collection
Its designers were primarily motivated by their shared dislike of Implementation Go, Assembly
C++.[25][26][27] language language (gc);
C++
Go was publicly announced in November 2009,[28] and version (gofrontend)
1.0 was released in March 2012.[29][30] Go is widely used in
OS DragonFly BSD,
production at Google[31] and in many other organizations and
FreeBSD,
open-source projects.
Linux, macOS,
NetBSD,
Branding and styling OpenBSD,[10]
Plan 9,[11]
e Gopher mascot was introduced in 2009 for the open source

1 of 23 5/9/24, 21:14
Go (programming language) - Wikipedia https://en.wikipedia.org/wiki/Go_(programming_language)

launch of the language. e design, by Renée French, borrowed Solaris,

from a c. 2000 WFMU promotion.[32] Windows
License 3-clause BSD[5]
In November 2016, the Go and Go Mono fonts were released by
+ patent
type designers Charles Bigelow and Kris Holmes specifically for
grant[12]
use by the Go project. Go is a humanist sans-serif resembling
Filename .go
Lucida Grande, and Go Mono is monospaced. Both fonts adhere
extensions
to the WGL4 character set and were designed to be legible with
a large x-height and distinct leerforms. Both Go and Go Mono Website go.dev (https://
adhere to the DIN 1450 standard by having a slashed zero, go.dev)
lowercase l with a tail, and an uppercase I with serifs.[33][34] Major implementations
gc, gofrontend
In April 2018, the original logo was redesigned by brand
designer Adam Smith. e new logo is a modern, stylized GO Influenced by

slanting right with trailing streamlines. (e Gopher mascot C, Oberon-2, Limbo, Active
remained the same.[35]) Oberon, communicating
sequential processes, Pascal,
Oberon, Smalltalk, Newsqueak,
Generics Modula-2, Alef, APL, BCPL,
e lack of support for generic programming in initial versions Modula, occam
of Go drew considerable criticism.[36] e designers expressed Influenced
an openness to generic programming and noted that built-in Crystal, V (Vlang)
functions were in fact type-generic, but are treated as special
cases; Pike called this a weakness that might be changed at some
point.[37] e Google team built at least one compiler for an
experimental Go dialect with generics, but did not release it.[38]

In August 2018, the Go principal contributors published dra

Mascot of Go programming
designs for generic programming and error handling and asked language is a Gopher shown
users to submit feedback.[39][40] However, the error handling above.
proposal was eventually abandoned.[41]

In June 2020, a new dra design document[42] was published that would add the necessary syntax to Go
for declaring generic functions and types. A code translation tool, go2go, was provided to allow users
to try the new syntax, along with a generics-enabled version of the online Go Playground.[43]

Generics were finally added to Go in version 1.18 on March 15, 2022.[44]

Versioning
Go 1 guarantees compatibility[45] for the language specification and major parts of the standard library.
All versions up through the current Go 1.22 release[46] have maintained this promise.

Go does not follow SemVer; rather, each major Go release is supported until there are two newer minor
releases. Unlike most soware, Go calls the second number in a version the major, i.e., in 1.x x is the
major version. [47] is is because Go plans to never reach 2.0, given that compatibility is one of
language's major selling points.[48]

Design

2 of 23 5/9/24, 21:14
Go (programming language) - Wikipedia https://en.wikipedia.org/wiki/Go_(programming_language)

Go is influenced by C (especially the Plan 9 dialect[49]), but with an emphasis on greater simplicity and
safety. It consists of:

▪ A syntax and environment adopting patterns more common in dynamic languages:[50]

▪ Optional concise variable declaration and initialization through type inference (x

:= 0 instead of var x int = 0; or var x = 0;)
▪ Fast compilation[51]
▪ Remote package management (go get)[52] and online package documentation[53]
▪ Distinctive approaches to particular problems:

▪ Built-in concurrency primitives: light-weight processes (goroutines), channels, and

the select statement
▪ An interface system in place of virtual inheritance, and type embedding instead of
non-virtual inheritance
▪ A toolchain that, by default, produces statically linked native binaries without
external Go dependencies
▪ A desire to keep the language specification simple enough to hold in a programmer's
head,[54] in part by omitting features that are common in similar languages.

Syntax
Go's syntax includes changes from C aimed at keeping code concise and readable. A combined
declaration/initialization operator was introduced that allows the programmer to write i := 3 or s
:= "Hello, world!", without specifying the types of variables used. is contrasts with C's int
i = 3; and const char *s = "Hello, world!";.

Semicolons still terminate statements;[b] but are implicit when the end of a line occurs.[c]

Methods may return multiple values, and returning a result, err pair is the conventional way a
method indicates an error to its caller in Go.[d] Go adds literal syntaxes for initializing struct
parameters by name and for initializing maps and slices. As an alternative to C's three-statement for
loop, Go's range expressions allow concise iteration over arrays, slices, strings, maps, and
channels.[57]

Types
Go has a number of built-in types, including numeric ones (byte, int64, float32, etc.), booleans,
and byte strings (string). Strings are immutable; built-in operators and keywords (rather than
functions) provide concatenation, comparison, and UTF-8 encoding/decoding.[58] Record types can be
defined with the struct keyword.[59]

For each type T and each non-negative integer constant n, there is an array type denoted [n]T; arrays
of differing lengths are thus of different types. Dynamic arrays are available as "slices", denoted []T for
some type T. ese have a length and a capacity specifying when new memory needs to be allocated to
expand the array. Several slices may share their underlying memory.[37][60][61]

3 of 23 5/9/24, 21:14
Go (programming language) - Wikipedia https://en.wikipedia.org/wiki/Go_(programming_language)

Pointers are available for all types, and the pointer-to-T type is denoted *T. Address-taking and
indirection use the & and * operators, as in C, or happen implicitly through the method call or aribute
access syntax.[62][63] ere is no pointer arithmetic,[e] except via the special unsafe.Pointer type
in the standard library.[64]

For a pair of types K, V, the type map[K]V is the type mapping type-K keys to type-V values, though
Go Programming Language specification does not give any performance guarantees or implementation
requirements for map types. Hash tables are built into the language, with special syntax and built-in
functions. chan T is a channel that allows sending values of type T between concurrent Go
processes.[65]

Aside from its support for interfaces, Go's type system is nominal: the type keyword can be used to
define a new named type, which is distinct from other named types that have the same layout (in the
case of a struct, the same members in the same order). Some conversions between types (e.g.,
between the various integer types) are pre-defined and adding a new type may define additional
conversions, but conversions between named types must always be invoked explicitly.[66] For example,
the type keyword can be used to define a type for IPv4 addresses, based on 32-bit unsigned integers as
follows:

type ipv4addr uint32

With this type definition, ipv4addr(x) interprets the uint32 value x as an IP address. Simply
assigning x to a variable of type ipv4addr is a type error.[67]

Constant expressions may be either typed or "untyped"; they are given a type when assigned to a typed
variable if the value they represent passes a compile-time check.[68]

Function types are indicated by the func keyword; they take zero or more parameters and return zero
or more values, all of which are typed. e parameter and return values determine a function type;
thus, func(string, int32) (int, error) is the type of functions that take a string and a
32-bit signed integer, and return a signed integer (of default width) and a value of the built-in interface
type error.[69]

Any named type has a method set associated with it. e IP address example above can be extended
with a method for checking whether its value is a known standard:

// ZeroBroadcast reports whether addr is 255.255.255.255.

func (addr ipv4addr) ZeroBroadcast() bool {
return addr == 0xFFFFFFFF
}

Due to nominal typing, this method definition adds a method to ipv4addr, but not on uint32.
While methods have special definition and call syntax, there is no distinct method type.[70]

Interface system
Go provides two features that replace class inheritance.

e first is embedding, which can be viewed as an automated form of composition.[71]

4 of 23 5/9/24, 21:14
Go (programming language) - Wikipedia https://en.wikipedia.org/wiki/Go_(programming_language)

e second are its interfaces, which provides runtime polymorphism.[72]:266 Interfaces are a class of
types and provide a limited form of structural typing in the otherwise nominal type system of Go. An
object which is of an interface type is also of another type, much like C++ objects being simultaneously
of a base and derived class. Go interfaces were designed aer protocols from the Smalltalk
programming language.[73] Multiple sources use the term duck typing when describing Go interfaces.
[74][75] Although the term duck typing is not precisely defined and therefore not wrong, it usually

implies that type conformance is not statically checked. Because conformance to a Go interface is
checked statically by the Go compiler (except when performing a type assertion), the Go authors prefer
the term structural typing.[76]

e definition of an interface type lists required methods by name and type. Any object of type T for
which functions exist matching all the required methods of interface type I is an object of type I as well.
e definition of type T need not (and cannot) identify type I. For example, if Shape, Square and
Circle are defined as

import "math"

type Shape interface {

Area() float64
}

type Square struct { // Note: no "implements" declaration

side float64
}

func (sq Square) Area() float64 { return sq.side * sq.side }

type Circle struct { // No "implements" declaration here either

radius float64
}

func (c Circle) Area() float64 { return math.Pi * math.Pow(c.radius, 2) }

then both a Square and a Circle are implicitly a Shape and can be assigned to a Shape-typed
variable.[72]:263–268 In formal language, Go's interface system provides structural rather than nominal
typing. Interfaces can embed other interfaces with the effect of creating a combined interface that is
satisfied by exactly the types that implement the embedded interface and any methods that the newly
defined interface adds.[72]:270

e Go standard library uses interfaces to provide genericity in several places, including the
input/output system that is based on the concepts of Reader and Writer.[72]:282–283

Besides calling methods via interfaces, Go allows converting interface values to other types with a run-
time type check. e language constructs to do so are the type assertion,[77] which checks against a
single potential type:

var shp Shape = Square{5}

square, ok := shp.(Square) // Asserts Square type on shp, should work
if ok {
fmt.Printf("%#v\n", square)
} else {
fmt.Println("Can't print shape as Square")
}

and the type switch,[78] which checks against multiple types:

5 of 23 5/9/24, 21:14
Go (programming language) - Wikipedia https://en.wikipedia.org/wiki/Go_(programming_language)

func (sq Square) Diagonal() float64 { return sq.side * math.Sqrt2 }

func (c Circle) Diameter() float64 { return 2 * c.radius }

func LongestContainedLine(shp Shape) float64 {

switch v := shp.(type) {
case Square:
return v.Diagonal() // Or, with type assertion, shp.(Square).Diagonal()
case Circle:
return v.Diameter() // Or, with type assertion, shp.(Circle).Diameter()
default:
return 0 // In practice, this should be handled with errors
}
}

e empty interface interface{} is an important base case because it can refer to an item of any
concrete type. It is similar to the Object class in Java or C# and is satisfied by any type, including
built-in types like int.[72]:284 Code using the empty interface cannot simply call methods (or built-in
operators) on the referred-to object, but it can store the interface{} value, try to convert it to a
more useful type via a type assertion or type switch, or inspect it with Go's reflect package.[79]
Because interface{} can refer to any value, it is a limited way to escape the restrictions of static
typing, like void* in C but with additional run-time type checks.

e interface{} type can be used to model structured data of any arbitrary schema in Go, such as
JSON or YAML data, by representing it as a map[string]interface{} (map of string to empty
interface). is recursively describes data in the form of a dictionary with string keys and values of any
type.[80]

Interface values are implemented using pointer to data and a second pointer to run-time type
information.[81] Like some other types implemented using pointers in Go, interface values are nil if
uninitialized.[82]

Generic code using parameterized types

Since version 1.18, Go supports generic code using parameterized types.[83]

Functions and types now have the ability to be generic using type parameters. ese type parameters
are specified within square brackets, right aer the function or type name.[84] e compiler transforms
the generic function or type into non-generic by substituting type arguments for the type parameters
provided, either explicitly by the user or type inference by the compiler.[85] is transformation process
is referred to as type instantiation.[86]

Interfaces now can define a set of types (known as type set) using | (Union) operator, as well as a set of
methods. ese changes were made to support type constraints in generics code. For a generic function
or type, a constraint can be thought of as the type of the type argument: a meta-type. is new ~T
syntax will be the first use of ~ as a token in Go. ~T means the set of all types whose underlying type is
T.[87]

type Number interface {

~int | ~float64 | ~float32 | ~int32 | ~int64
}

func Add[T Number](nums ...T) T {

var sum T
for _, v := range nums {
sum += v
}

6 of 23 5/9/24, 21:14
Go (programming language) - Wikipedia https://en.wikipedia.org/wiki/Go_(programming_language)

return sum
}

func main() {
add := Add[int] // Type instantiation
println(add(1, 2, 3, 4, 5)) // 15

res := Add(1.1, 2.2, 3.3, 4.4, 5.5) // Type Inference

println(res) // +1.650000e+001
}

Enumerated types
Go uses the iota keyword to create enumerated constants.[88]

type ByteSize float64

const (
_ = iota // ignore first value by assigning to blank identifier
KB ByteSize = 1 << (10 * iota)
MB
GB
)

Package system
In Go's package system, each package has a path (e.g., "compress/bzip2" or "golang.org/x
/net/html") and a name (e.g., bzip2 or html). References to other packages' definitions must
always be prefixed with the other package's name, and only the capitalized names from other packages
are accessible: io.Reader is public but bzip2.reader is not.[89] e go get command can
retrieve packages stored in a remote repository[90] and developers are encouraged to develop packages
inside a base path corresponding to a source repository (such as example.com/user_name
/package_name) to reduce the likelihood of name collision with future additions to the standard library
or other external libraries.[91]

Concurrency: goroutines and channels

e Go language has built-in facilities, as well as library support, for writing concurrent programs.
Concurrency refers not only to CPU parallelism, but also to asynchrony: leing slow operations like a
database or network read run while the program does other work, as is common in event-based
servers.[92]

e primary concurrency construct is the goroutine, a type of green thread.[93]:280–281 A function call
prefixed with the go keyword starts a function in a new goroutine. e language specification does not
specify how goroutines should be implemented, but current implementations multiplex a Go process's
goroutines onto a smaller set of operating-system threads, similar to the scheduling performed in
Erlang.[94]:10

While a standard library package featuring most of the classical concurrency control structures (mutex
locks, etc.) is available,[94]:151–152 idiomatic concurrent programs instead prefer channels, which send
messages between goroutines.[95] Optional buffers store messages in FIFO order[96]:43 and allow
sending goroutines to proceed before their messages are received.[93]:233

Channels are typed, so that a channel of type chan T can only be used to transfer messages of type T.

7 of 23 5/9/24, 21:14
Go (programming language) - Wikipedia https://en.wikipedia.org/wiki/Go_(programming_language)

Special syntax is used to operate on them; <-ch is an expression that causes the executing goroutine to
block until a value comes in over the channel ch, while ch <- x sends the value x (possibly blocking
until another goroutine receives the value). e built-in switch-like select statement can be used
to implement non-blocking communication on multiple channels; see below for an example. Go has a
memory model describing how goroutines must use channels or other operations to safely share
data.[97]

e existence of channels does not by itself set Go apart from actor model-style concurrent languages
like Erlang, where messages are addressed directly to actors (corresponding to goroutines). In the actor
model, channels are themselves actors, therefore addressing a channel just means to address an actor.
e actor style can be simulated in Go by maintaining a one-to-one correspondence between
goroutines and channels, but the language allows multiple goroutines to share a channel or a single
goroutine to send and receive on multiple channels.[94]:147

From these tools one can build concurrent constructs like worker pools, pipelines (in which, say, a file
is decompressed and parsed as it downloads), background calls with timeout, "fan-out" parallel calls to
a set of services, and others.[98] Channels have also found uses further from the usual notion of
interprocess communication, like serving as a concurrency-safe list of recycled buffers,[99]
implementing coroutines (which helped inspire the name goroutine),[100] and implementing
iterators.[101]

Concurrency-related structural conventions of Go (channels and alternative channel inputs) are derived
from Tony Hoare's communicating sequential processes model. Unlike previous concurrent
programming languages such as Occam or Limbo (a language on which Go co-designer Rob Pike
worked),[102] Go does not provide any built-in notion of safe or verifiable concurrency.[103] While the
communicating-processes model is favored in Go, it is not the only one: all goroutines in a program
share a single address space. is means that mutable objects and pointers can be shared between
goroutines; see § Lack of data race safety, below.

Suitability for parallel programming

Although Go's concurrency features are not aimed primarily at parallel processing,[92] they can be used
to program shared-memory multi-processor machines. Various studies have been done into the
effectiveness of this approach.[104] One of these studies compared the size (in lines of code) and speed
of programs wrien by a seasoned programmer not familiar with the language and corrections to these
programs by a Go expert (from Google's development team), doing the same for Chapel, Cilk and Intel
TBB. e study found that the non-expert tended to write divide-and-conquer algorithms with one go
statement per recursion, while the expert wrote distribute-work-synchronize programs using one
goroutine per processor core. e expert's programs were usually faster, but also longer.[105]

Lack of data race safety

Go's approach to concurrency can be summarized as "don't communicate by sharing memory; share
memory by communicating".[106] ere are no restrictions on how goroutines access shared data,
making data races possible. Specifically, unless a program explicitly synchronizes via channels or other
means, writes from one goroutine might be partly, entirely, or not at all visible to another, oen with no
guarantees about ordering of writes.[103] Furthermore, Go's internal data structures like interface values,
slice headers, hash tables, and string headers are not immune to data races, so type and memory safety
can be violated in multithreaded programs that modify shared instances of those types without

8 of 23 5/9/24, 21:14
Go (programming language) - Wikipedia https://en.wikipedia.org/wiki/Go_(programming_language)

synchronization.[107][108] Instead of language support, safe concurrent programming thus relies on

conventions; for example, Chisnall recommends an idiom called "aliases xor mutable", meaning that
passing a mutable value (or pointer) over a channel signals a transfer of ownership over the value to its
receiver.[94]:155 e gc toolchain has an optional data race detector that can check for unsynchronized
access to shared memory during runtime since version 1.1,[109] additionally a best-effort race detector is
also included by default since version 1.6 of the gc runtime for access to the map data type.[110]

Binaries
e linker in the gc toolchain creates statically linked binaries by default; therefore all Go binaries
include the Go runtime.[111][112]

Omissions
Go deliberately omits certain features common in other languages, including
(implementation) inheritance, assertions,[] pointer arithmetic,[e] implicit type conversions, untagged
unions,[g] and tagged unions.[h] e designers added only those facilities that all three agreed on.[115]

Of the omied language features, the designers explicitly argue against assertions and pointer
arithmetic, while defending the choice to omit type inheritance as giving a more useful language,
encouraging instead the use of interfaces to achieve dynamic dispatch[i] and composition to reuse code.
Composition and delegation are in fact largely automated by struct embedding; according to
researchers Schmager et al., this feature "has many of the drawbacks of inheritance: it affects the public
interface of objects, it is not fine-grained (i.e, no method-level control over embedding), methods of
embedded objects cannot be hidden, and it is static", making it "not obvious" whether programmers will
overuse it to the extent that programmers in other languages are reputed to overuse inheritance.[71]

Exception handling was initially omied in Go due to lack of a "design that gives value proportionate
to the complexity".[116] An exception-like panic/recover mechanism that avoids the usual try-
catch control structure was proposed[117] and released in the March 30, 2010 snapshot.[118] e Go
authors advise using it for unrecoverable errors such as those that should halt an entire program or
server request, or as a shortcut to propagate errors up the stack within a package.[119][120] Across
package boundaries, Go includes a canonical error type, and multi-value returns using this type are the
standard idiom.[4]

Style
e Go authors put substantial effort into influencing the style of Go programs:

▪ Indentation, spacing, and other surface-level details of code are automatically

standardized by the gofmt tool. It uses tabs for indentation and blanks for alignment.
Alignment assumes that an editor is using a fixed-width font.[121] golint does
additional style checks automatically, but has been deprecated and archived by the Go
maintainers.[122]
▪ Tools and libraries distributed with Go suggest standard approaches to things like API
documentation (godoc),[123] testing (go test), building (go build), package
management (go get), and so on.
▪ Go enforces rules that are recommendations in other languages, for example banning

9 of 23 5/9/24, 21:14
Go (programming language) - Wikipedia https://en.wikipedia.org/wiki/Go_(programming_language)

cyclic dependencies, unused variables[124] or imports,[125] and implicit type

conversions.
▪ The omission of certain features (for example, functional-programming shortcuts like
map and Java-style try/finally blocks) tends to encourage a particular explicit,
concrete, and imperative programming style.
▪ On day one the Go team published a collection of Go idioms,[123] and later also
collected code review comments,[126] talks,[127] and official blog posts[128] to teach Go
style and coding philosophy.

Tools
e main Go distribution includes tools for building, testing, and analyzing code:

▪ go build, which builds Go binaries using only information in the source files
themselves, no separate makefiles
▪ go test, for unit testing and microbenchmarks as well as fuzzing
▪ go fmt, for formatting code
▪ go install, for retrieving and installing remote packages
▪ go vet, a static analyzer looking for potential errors in code
▪ go run, a shortcut for building and executing code
▪ godoc, for displaying documentation or serving it via HTTP
▪ gorename, for renaming variables, functions, and so on in a type-safe way
▪ go generate, a standard way to invoke code generators
▪ go mod, for creating a new module, adding dependencies, upgrading dependencies,
etc.
It also includes profiling and debugging support, fuzzing capabilities to detect bugs, runtime
instrumentation (for example, to track garbage collection pauses), and a data race detector.

Another tool maintained by the Go team but is not included in Go distributions is gopls, a language
server that provides IDE features such as intelligent code completion to Language Server Protocol
compatible editors.[129]

An ecosystem of third-party tools adds to the standard distribution, such as gocode, which enables
code autocompletion in many text editors, goimports, which automatically adds/removes package
imports as needed, and errcheck, which detects code that might unintentionally ignore errors.

Examples

Hello world

package main

import "fmt"

func main() {
fmt.Println("hello world")

10 of 23 5/9/24, 21:14
Go (programming language) - Wikipedia https://en.wikipedia.org/wiki/Go_(programming_language)

where "fmt" is the package for formaed I/O, similar to C's C file input/output.[130]

Concurrency
e following simple program demonstrates Go's concurrency features to implement an asynchronous
program. It launches two lightweight threads ("goroutines"): one waits for the user to type some text,
while the other implements a timeout. e select statement waits for either of these goroutines to
send a message to the main routine, and acts on the first message to arrive (example adapted from
David Chisnall's book).[94]:152

package main

import (
"fmt"
"time"
)

func readword(ch chan string) {

fmt.Println("Type a word, then hit Enter.")
var word string
fmt.Scanf("%s", &word)
ch <- word
}

func timeout(t chan bool) {

time.Sleep(5 * time.Second)
t <- false
}

func main() {
t := make(chan bool)
go timeout(t)

ch := make(chan string)
go readword(ch)

select {
case word := <-ch:
fmt.Println("Received", word)
case <-t:
fmt.Println("Timeout.")
}
}

Testing
e testing package provides support for automated testing of go packages.[131] Target function
example:

func ExtractUsername(email string) string {

at := strings.Index(email, "@")
return email[:at]
}

Test code (note that assert keyword is missing in Go; tests live in <filename>_test.go at the same
package):

import (
"testing"
)

11 of 23 5/9/24, 21:14
Go (programming language) - Wikipedia https://en.wikipedia.org/wiki/Go_(programming_language)

func TestExtractUsername(t *testing.T) {

t.Run("withoutDot", func(t *testing.T) {
username := ExtractUsername("r@google.com")
if username != "r" {
t.Fatalf("Got: %v\n", username)
}
})

t.Run("withDot", func(t *testing.T) {

username := ExtractUsername("jonh.smith@example.com")
if username != "jonh.smith" {
t.Fatalf("Got: %v\n", username)
}
})
}

It is possible to run tests in parallel.

Web app
e net/hp package provides support for creating web applications.

is example would show "Hello world!" when localhost:8080 is visited.

package main

import (
"fmt"
"log"
"net/http"
)

func helloFunc(w http.ResponseWriter, r *http.Request) {

fmt.Fprintf(w, "Hello world!")
}

func main() {
http.HandleFunc("/", helloFunc)
log.Fatal(http.ListenAndServe(":8080", nil))
}

Applications
Go has found widespread adoption in various domains due to its robust standard library and ease of
use.[132]

Popular applications include: Caddy, a web server that automates the process of seing up HTTPS,[133]
Docker, which provides a platform for containerization, aiming to ease the complexities of soware
development and deployment,[134] Kubernetes, which automates the deployment, scaling, and
management of containerized applications,[135] CockroachDB, a distributed SQL database engineered
for scalability and strong consistency,[136] and Hugo, a static site generator that prioritizes speed and
flexibility, allowing developers to create websites efficiently.[137]

For further examples, please also see related query to Wikidata (hps://query.wikidata.org/#SELECT%2
0DISTINCT%20%3Finstance_of%20%3Finstance_ofDescription%20%3Finstance_ofLabel%20%3Fofficial_w
ebsite%0AWHERE%20%7B%0A%20%20SERVICE%20wikibase%3Alabel%20%7B%20bd%3AserviceParam%
20wikibase%3Alanguage%20%22%5BAUTO_LANGUAGE%5D%2Cen%22.%20%7D%0A%20%20%3Finstanc
e_of%20wdt%3AP31%2Fwdt%3AP279%2a%20wd%3AQ341%0A%20%20OPTIONAL%20%7B%20%3Finstanc
e_of%20wdt%3AP856%20%3Fofficial_website%20%7D%0A%20%20%3Finstance_of%20wdt%3AP277%20w

12 of 23 5/9/24, 21:14
Go (programming language) - Wikipedia https://en.wikipedia.org/wiki/Go_(programming_language)

d%3AQ37227.%0A%7D)

Reception
e interface system, and the deliberate omission of inheritance, were praised by Michele Simionato,
who likened these characteristics to those of Standard ML, calling it "a shame that no popular language
has followed [this] particular route".[138]

Dave Astels at Engine Yard wrote in 2009:[139]

Go is extremely easy to dive into. ere are a minimal number of fundamental language
concepts and the syntax is clean and designed to be clear and unambiguous. Go is still
experimental and still a lile rough around the edges.

Go was named Programming Language of the Year by the TIOBE Programming Community Index in its
first year, 2009, for having a larger 12-month increase in popularity (in only 2 months, aer its
introduction in November) than any other language that year, and reached 13th place by January
2010,[140] surpassing established languages like Pascal. By June 2015, its ranking had dropped to below
50th in the index, placing it lower than COBOL and Fortran.[141] But as of January 2017, its ranking had
surged to 13th, indicating significant growth in popularity and adoption. Go was again awarded TIOBE
Programming Language of the Year in 2016.

Bruce Eckel has stated:[142]

e complexity of C++ (even more complexity has been added in the new C++), and the
resulting impact on productivity, is no longer justified. All the hoops that the C++
programmer had to jump through in order to use a C-compatible language make no sense
anymore -- they're just a waste of time and effort. Go makes much more sense for the class of
problems that C++ was originally intended to solve.

A 2011 evaluation of the language and its gc implementation in comparison to C++ (GCC), Java and
Scala by a Google engineer found:

Go offers interesting language features, which also allow for a concise and standardized
notation. e compilers for this language are still immature, which reflects in both
performance and binary sizes.

—R. Hundt[143]

e evaluation got a rebual from the Go development team. Ian Lance Taylor, who had improved the
Go code for Hundt's paper, had not been aware of the intention to publish his code, and says that his
version was "never intended to be an example of idiomatic or efficient Go"; Russ Cox then optimized
the Go code, as well as the C++ code, and got the Go code to run almost as fast as the C++ version and
more than an order of magnitude faster than the code in the paper.[144]

▪ Go's nil combined with the lack of algebraic types leads to difficulty handling failures
and base cases.[145][146]

13 of 23 5/9/24, 21:14
Go (programming language) - Wikipedia https://en.wikipedia.org/wiki/Go_(programming_language)

▪ Go does not allow an opening brace to appear on its own line, which forces all Go
programmers to use the same brace style.[147]
▪ Go has been criticized for focusing on simplicity of implementation rather than
correctness and flexibility; as an example, the language uses POSIX file semantics on
all platforms, and therefore provides incorrect information on platforms such as
Windows (which do not follow the aforementioned standard).[148][149]
▪ A study showed that it is as easy to make concurrency bugs with message passing as
with shared memory, sometimes even more.[150]

Naming dispute
On November 10, 2009, the day of the general release of the language, Francis McCabe, developer of the
Go! programming language (note the exclamation point), requested a name change of Google's
language to prevent confusion with his language, which he had spent 10 years developing.[151] McCabe
raised concerns that "the 'big guy' will end up steam-rollering over" him, and this concern resonated
with the more than 120 developers who commented on Google's official issues thread saying they
should change the name, with some[152] even saying the issue contradicts Google's moo of: Don't be
evil.[153]

On October 12, 2010, the filed public issue ticket was closed by Google developer Russ Cox (@rsc) with
the custom status "Unfortunate" accompanied by the following comment:

"ere are many computing products and services named Go. In the 11 months since our
release, there has been minimal confusion of the two languages."[153]

See also
Free and open-
source software
portal

▪ Fat pointer
▪ Comparison of programming languages

Notes
a. Using alternative backends reduces compilation speed and Go's control over garbage
collection but provides better machine-code optimization.[20]
b. But "To allow complex statements to occupy a single line, a semicolon may be omitted
before a closing ) or }".[55]
c. "if the newline comes after a token that could end a statement, [the lexer will] insert a
semicolon".[56]
d. Usually, exactly one of the result and error values has a value other than the type's
zero value; sometimes both do, as when a read or write can only be partially
completed, and sometimes neither, as when a read returns 0 bytes. See Semipredicate
problem: Multivalued return.
e. Language FAQ "Why is there no pointer arithmetic? Safety ... never derive an illegal

14 of 23 5/9/24, 21:14
Go (programming language) - Wikipedia https://en.wikipedia.org/wiki/Go_(programming_language)

address that succeeds incorrectly ... using array indices can be as efficient as ... pointer
arithmetic ... simplify the implementation of the garbage collector...."[4]
f. Language FAQ "Why does Go not have assertions? ...our experience has been that
programmers use them as a crutch to avoid thinking about proper error handling and
reporting...."[4]
g. Language FAQ "Why are there no untagged unions...? [they] would violate Go's
memory safety guarantees."[4]
h. Language FAQ "Why does Go not have variant types? ... We considered [them but] they
overlap in confusing ways with interfaces.... [S]ome of what variant types address is
already covered, ... although not as elegantly."[4] (The tag of an interface type[113] is
accessed with a type assertion[114]).
i. Questions "How do I get dynamic dispatch of methods?" and "Why is there no type
inheritance?" in the language FAQ.[4]

References
1. "Codewalk: First-Class Functions in Go" (https://go.dev/doc/codewalk/functions/). "Go
supports first class functions, higher-order functions, user-defined function types,
function literals, closures, and multiple return values. This rich feature set supports a
functional programming style in a strongly typed language."
2. "Is Go an object-oriented language?" (https://golang.org/doc/faq#Is_Go_an_object-orie
nted_language). Retrieved April 13, 2019. "Although Go has types and methods and
allows an object-oriented style of programming, there is no type hierarchy."
3. "Go: code that grows with grace" (https://talks.golang.org/2012/chat.slide#5).
Retrieved June 24, 2018. "Go is Object Oriented, but not in the usual way."
4. "Language Design FAQ" (https://golang.org/doc/go_faq.html). The Go Programming
Language. January 16, 2010. Retrieved February 27, 2010.
5. "Text file LICENSE" (https://golang.org/LICENSE). The Go Programming Language.
Retrieved October 5, 2012.
6. "Release History" (https://go.dev/doc/devel/release#go1.22.0).
7. "The Go Programming Language Specification - the Go Programming Language" (http
s://go.dev/ref/spec#Introduction).
8. "Why doesn't Go have "implements" declarations?" (https://golang.org/doc/faq#imple
ments_interface). The Go Programming Language. Retrieved October 1, 2015.
9. Pike, Rob (December 22, 2014). "Rob Pike on Twitter" (https://web.archive.org/web/202
20407025913/https://twitter.com/rob_pike/status/546973312543227904). Archived
from the original (https://twitter.com/rob_pike/status/546973312543227904) on April 7,
2022. Retrieved March 13, 2016. "Go has structural typing, not duck typing. Full
interface satisfaction is checked and required."
10. "lang/go: go-1.4" (http://ports.su/lang/go). OpenBSD ports. December 23, 2014.
Retrieved January 19, 2015.
11. "Go Porting Efforts" (http://go-lang.cat-v.org/os-ports). Go Language Resources. cat-v.
January 12, 2010. Retrieved January 18, 2010.
12. "Additional IP Rights Grant" (https://golang.org/PATENTS). The Go Programming
Language. Retrieved October 5, 2012.
13. Kincaid, Jason (November 10, 2009). "Google's Go: A New Programming Language
That's Python Meets C++" (https://techcrunch.com/2009/11/10/google-go-language/).
TechCrunch. Retrieved January 18, 2010.
14. Metz, Cade (May 5, 2011). "Google Go boldly goes where no code has gone before" (htt
ps://www.theregister.co.uk/2011/05/05/google_go/). The Register.

15 of 23 5/9/24, 21:14
Go (programming language) - Wikipedia https://en.wikipedia.org/wiki/Go_(programming_language)

15. "Is the language called Go or Golang?" (https://go.dev/doc/faq#go_or_golang).

Retrieved March 16, 2022. "The language is called Go."
16. "Go 1.5 Release Notes" (https://golang.org/doc/go1.5#implementation). Retrieved
January 28, 2016. "The compiler and runtime are now implemented in Go and
assembler, without C."
17. "Go 1.11 is Released" (https://blog.golang.org/go1.11). August 24, 2018. Retrieved
January 1, 2019.
18. "Installing GCC: Configuration" (https://gcc.gnu.org/install/configure.html). Retrieved
December 3, 2011. "Ada, Go and Objective-C++ are not default languages"
19. "FAQ: Implementation" (https://golang.org/doc/go_faq.html#Implementation). The Go
Programming Language. August 2, 2021. Retrieved August 2, 2021.
20. "gollvm § Is gollvm a replacement for the main Go compiler? (gc)" (https://go.googleso
urce.com/gollvm/). Git at Google.
21. "A compiler from Go to JavaScript for running Go code in a browser:
Gopherjs/Gopherjs" (https://github.com/gopherjs/gopherjs). GitHub. Archived (https://
web.archive.org/web/20231212143621/https://github.com/gopherjs/gopherjs) from
the original on December 12, 2023.
22. "Go at Google: Language Design in the Service of Software Engineering" (https://talks.
golang.org/2012/splash.article). Retrieved October 8, 2018.
23. Pike, Rob (April 28, 2010). "Another Go at Language Design" (http://www.stanford.edu/
class/ee380/Abstracts/100428.html). Stanford EE Computer Systems Colloquium. Stanford
University. Video available (https://www.youtube.com/watch?v=7VcArS4Wpqk).
24. "Frequently Asked Questions (FAQ) - The Go Programming Language" (https://golang.o
rg/doc/faq#different_syntax). The Go Programming Language. Retrieved February 26,
2016.
25. Binstock, Andrew (May 18, 2011). "Dr. Dobb's: Interview with Ken Thompson" (https://w
eb.archive.org/web/20130105013259/https://www.drdobbs.com/open-source/intervie
w-with-ken-thompson/229502480). Archived from the original (http://www.drdobbs.co
m/open-source/interview-with-ken-thompson/229502480) on January 5, 2013.
Retrieved February 7, 2014.
26. Pike, Rob (2012). "Less is exponentially more" (http://commandcenter.blogspot.mx/201
2/06/less-is-exponentially-more.html).
27. Griesemer, Robert (2015). "The Evolution of Go" (https://talks.golang.org/2015/gopherc
on-goevolution.slide#4).
28. Griesemer, Robert; Pike, Rob; Thompson, Ken; Taylor, Ian; Cox, Russ; Kim, Jini; Langley,
Adam. "Hey! Ho! Let's Go!" (https://opensource.googleblog.com/2009/11/hey-ho-lets-g
o.html). Google Open Source. Retrieved May 17, 2018.
29. Shankland, Stephen (March 30, 2012). "Google's Go language turns one, wins a spot at
YouTube: The lower-level programming language has matured enough to sport the 1.0
version number. And it's being used for real work at Google" (https://www.cnet.com/ne
ws/googles-go-language-turns-one-wins-a-spot-at-youtube/). News. CNet. CBS
Interactive Inc. Retrieved August 6, 2017. "Google has released version 1 of its Go
programming language, an ambitious attempt to improve upon giants of the lower-
level programming world such as C and C++."
30. "Release History" (https://golang.org/doc/devel/release.html). The Go Programming
Language.
31. "Go FAQ: Is Google using Go internally?" (https://golang.org/doc/faq#internal_usage).
Retrieved March 9, 2013.
32. "The Go Gopher - The Go Programming Language" (https://go.dev/blog/gopher).
go.dev. Retrieved February 9, 2023.

16 of 23 5/9/24, 21:14
Go (programming language) - Wikipedia https://en.wikipedia.org/wiki/Go_(programming_language)

33. "Go fonts" (https://blog.golang.org/go-fonts). Go. November 16, 2016. Retrieved

March 12, 2019.
34. "Go Font TTFs" (https://github.com/golang/image/tree/master/font/gofont/ttfs).
GitHub. Retrieved April 2, 2019.
35. "Go's New Brand" (https://blog.golang.org/go-brand). The Go Blog. Retrieved
November 9, 2018.
36. Merrick, Alice (March 9, 2021). "Go Developer Survey 2020 Results" (https://go.dev/blog
/survey2020-results#:~:text=Among%20the%2026%25%20of%20respondents%20wh
o%20said%20Go%20lacks%20language%20features%20they%20need%2C%2088%25%
20selected%20generics%20as%20a%20critical%20missing%20feature.). Go
Programming Language. Retrieved March 16, 2022.
37. Pike, Rob (September 26, 2013). "Arrays, slices (and strings): The mechanics of
'append' " (https://blog.golang.org/slices). The Go Blog. Retrieved March 7, 2015.
38. "E2E: Erik Meijer and Robert Griesemer" (http://channel9.msdn.com/Blogs/Charles/Erik
-Meijer-and-Robert-Griesemer-Go). Channel 9. Microsoft. May 7, 2012.
39. "Go 2 Draft Designs" (https://go.googlesource.com/proposal/+/master/design/go2draf
t.md). Retrieved September 12, 2018.
40. "The Go Blog: Go 2 Draft Designs" (https://blog.golang.org/go2draft). August 28, 2018.
41. "Proposal: A built-in Go error check function, "try" " (https://github.com/golang/go/issu
es/32437). Go repository on GitHub. Retrieved March 16, 2022.
42. "Type Parameters — Draft Design" (https://go.googlesource.com/proposal/+/refs/head
s/master/design/go2draft-type-parameters.md). go.googlesource.com.
43. "Generics in Go" (https://bitfieldconsulting.com/golang/generics).
bitfieldconsulting.com. December 17, 2021.
44. "Go 1.18 is released!" (https://go.dev/blog/go1.18). Go Programming Language. March
15, 2022. Retrieved March 16, 2022.
45. "Go 1 and the Future of Go Programs" (https://golang.org/doc/go1compat). The Go
Programming Language.
46. "Go 1.22 Release Notes" (https://go.dev/doc/go1.22). The Go Programming Language.
47. "Release History" (https://golang.org/doc/devel/release.html#policy). The Go
Programming Language.
48. "Backward Compatibility, Go 1.21, and Go 2" (https://go.dev/blog/compat). The Go
Programming Language.
49. "A Quick Guide to Go's Assembler" (https://go.dev/doc/asm). go.dev. Retrieved
December 31, 2021.
50. Pike, Rob. "The Go Programming Language" (https://www.youtube.com/watch?v=rKnD
gT73v8s). YouTube. Retrieved July 1, 2011.
51. Pike, Rob (November 10, 2009). The Go Programming Language (https://www.youtube.c
om/watch?v=rKnDgT73v8s#t=8m53) (flv) (Tech talk). Google. Event occurs at 8:53.
52. "Download and install packages and dependencies" (https://golang.org/cmd/go/#hdr-
Download_and_install_packages_and_dependencies). See godoc.org (http://godoc.org)
for addresses and documentation of some packages.
53. "GoDoc" (http://godoc.org). godoc.org.
54. Pike, Rob. "The Changelog" (https://web.archive.org/web/20131020101046/http://5by
5.tv/changelog/100) (Podcast). Archived from the original (http://5by5.tv/changelog/10
0) on October 20, 2013. Retrieved October 7, 2013.
55. "Go Programming Language Specification, §Semicolons" (https://golang.org/ref/spec#
Semicolons). The Go Programming Language.

17 of 23 5/9/24, 21:14
Go (programming language) - Wikipedia https://en.wikipedia.org/wiki/Go_(programming_language)

56. "Effective Go, §Semicolons" (https://golang.org/doc/effective_go.html#semicolons).

The Go Programming Language.
57. "The Go Programming Language Specification" (https://golang.org/ref/spec#For_state
ments). The Go Programming Language.
58. Pike, Rob (October 23, 2013). "Strings, bytes, runes and characters in Go" (https://blog.
golang.org/strings).
59. Doxsey, Caleb. "Structs and Interfaces — An Introduction to Programming in Go" (http
s://www.golang-book.com/books/intro/9). www.golang-book.com. Retrieved October 15,
2018.
60. Gerrand, Andrew. "Go Slices: usage and internals" (https://blog.golang.org/go-slices-us
age-and-internals).
61. The Go Authors. "Effective Go: Slices" (https://golang.org/doc/effective_go.html#slices).
62. The Go authors. "Selectors" (https://golang.org/ref/spec#Selectors).
63. The Go authors. "Calls" (https://golang.org/ref/spec#Calls).
64. "Go Programming Language Specification, §Package unsafe" (https://golang.org/ref/sp
ec#Package_unsafe). The Go Programming Language.
65. "The Go Programming Language Specification" (https://go.dev/ref/spec#Channel_type
s). go.dev. Retrieved December 31, 2021.
66. "The Go Programming Language Specification" (https://golang.org/ref/spec#Assignabi
lity). The Go Programming Language.
67. "A tour of go" (https://go.dev/tour/basics/13). go.dev.
68. "The Go Programming Language Specification" (https://golang.org/ref/spec#Constant
s). The Go Programming Language.
69. "The Go Programming Language Specification" (https://go.dev/ref/spec#Function_type
s). go.dev. Retrieved December 31, 2021.
70. "The Go Programming Language Specification" (https://golang.org/ref/spec#Calls). The
Go Programming Language.
71. Schmager, Frank; Cameron, Nicholas; Noble, James (2010). GoHotDraw: evaluating the
Go programming language with design patterns. Evaluation and Usability of
Programming Languages and Tools. ACM.
72. Balbaert, Ivo (2012). The Way to Go: A Thorough Introduction to the Go Programming
Language. iUniverse.
73. "The Evolution of Go" (https://talks.golang.org/2015/gophercon-goevolution.slide#19).
talks.golang.org. Retrieved March 13, 2016.
74. Diggins, Christopher (November 24, 2009). "Duck Typing and the Go Programming
Language" (http://www.drdobbs.com/architecture-and-design/duck-typing-and-the-go-
programming-langu/228701527). Dr. Dobb's, The world of software development.
Retrieved March 10, 2016.
75. Ryer, Mat (December 1, 2015). "Duck typing in Go" (https://medium.com/@matryer/gol
ang-advent-calendar-day-one-duck-typing-a513aaed544d#.ebm7j81xu). Retrieved
March 10, 2016.
76. "Frequently Asked Questions (FAQ) - The Go Programming Language" (https://golang.o
rg/doc/faq). The Go Programming Language.
77. "The Go Programming Language Specification" (https://golang.org/ref/spec#Type_ass
ertions). The Go Programming Language.
78. "The Go Programming Language Specification" (https://golang.org/ref/spec#Type_swit
ches). The Go Programming Language.
79. "reflect package" (https://pkg.go.dev/reflect). pkg.go.dev.

18 of 23 5/9/24, 21:14
Go (programming language) - Wikipedia https://en.wikipedia.org/wiki/Go_(programming_language)

80. "map[string]interface{} in Go" (https://bitfieldconsulting.com/golang/map-string-interf

ace). bitfieldconsulting.com. June 6, 2020.
81. "Go Data Structures: Interfaces" (http://research.swtch.com/interfaces). Retrieved
November 15, 2012.
82. "The Go Programming Language Specification" (https://golang.org/ref/spec#Interface_
types). The Go Programming Language.
83. "Go 1.18 Release Notes: Generics" (https://go.dev/doc/go1.18#generics). Go
Programming Language. March 15, 2022. Retrieved March 16, 2022.
84. "Type Parameters Proposal" (https://go.googlesource.com/proposal/+/HEAD/design/4
3651-type-parameters.md). go.googlesource.com. Retrieved June 25, 2023.
85. "The Go Programming Language Specification - The Go Programming Language" (http
s://go.dev/ref/spec). go.dev. Retrieved June 25, 2023.
86. "An Introduction To Generics - The Go Programming Language" (https://go.dev/blog/in
tro-generics). go.dev. Retrieved June 25, 2023.
87. "Type Parameters Proposal" (https://go.googlesource.com/proposal/+/HEAD/design/4
3651-type-parameters.md#using-a-constraint). go.googlesource.com. Retrieved June 25,
2023.
88. "Effective Go" (https://golang.org/doc/effective_go.html#constants). golang.org. The
Go Authors. Retrieved May 13, 2014.
89. "A Tutorial for the Go Programming Language" (https://golang.org/doc/go_tutorial.ht
ml). The Go Programming Language. Retrieved March 10, 2013. "In Go the rule about
visibility of information is simple: if a name (of a top-level type, function, method,
constant or variable, or of a structure field or method) is capitalized, users of the
package may see it. Otherwise, the name and hence the thing being named is visible
only inside the package in which it is declared."
90. "go" (https://golang.org/cmd/go/#hdr-Download_and_install_packages_and_dependen
cies). The Go Programming Language.
91. "How to Write Go Code" (https://golang.org/doc/code.html). The Go Programming
Language. "The packages from the standard library are given short import paths such
as "fmt" and "net/http". For your own packages, you must choose a base path that is
unlikely to collide with future additions to the standard library or other external
libraries. If you keep your code in a source repository somewhere, then you should use
the root of that source repository as your base path. For instance, if you have an
Example account at example.com/user, that should be your base path"
92. Pike, Rob (September 18, 2012). "Concurrency is not Parallelism" (https://vimeo.com/49
718712).
93. Donovan, Alan A. A.; Kernighan, Brian W. (2016). The Go programming language.
Addison-Wesley professional computing series. New York, Munich: Addison-Wesley.
ISBN 978-0-13-419044-0.
94. Chisnall, David (2012). The Go Programming Language Phrasebook (https://books.googl
e.com/books?id=scyH562VXZUC). Addison-Wesley. ISBN 9780132919005.
95. "Effective Go" (https://golang.org/doc/effective_go.html#sharing). The Go Programming
Language.
96. Summerfield, Mark (2012). Programming in Go: Creating Applications for the 21st Century.
Addison-Wesley.
97. "The Go Memory Model" (https://golang.org/ref/mem). Retrieved April 10, 2017.
98. "Go Concurrency Patterns" (https://talks.golang.org/2012/concurrency.slide). The Go
Programming Language.
99. Graham-Cumming, John (August 24, 2013). "Recycling Memory Buffers in Go" (https://b
log.cloudflare.com/recycling-memory-buffers-in-go).

19 of 23 5/9/24, 21:14
Go (programming language) - Wikipedia https://en.wikipedia.org/wiki/Go_(programming_language)

100. "tree.go" (https://golang.org/doc/play/tree.go).

101. Cheslack-Postava, Ewen. "Iterators in Go" (http://ewencp.org/blog/golang-iterators/).
102. Kernighan, Brian W. "A Descent Into Limbo" (http://www.vitanuova.com/inferno/papers
/descent.html).
103. "The Go Memory Model" (https://golang.org/doc/go_mem.html). Retrieved January 5,
2011.
104. Tang, Peiyi (2010). Multi-core parallel programming in Go (https://web.archive.org/web/2
0160909032631/http://www.ualr.edu/pxtang/papers/acc10.pdf) (PDF). Proc. First
International Conference on Advanced Computing and Communications. Archived
from the original (http://www.ualr.edu/pxtang/papers/acc10.pdf) (PDF) on September
9, 2016. Retrieved May 14, 2015.
105. Nanz, Sebastian; West, Scott; Soares Da Silveira, Kaue. Examining the expert gap in
parallel programming (http://se.inf.ethz.ch/people/west/expert-gap-europar-2013.pdf)
(PDF). Euro-Par 2013. CiteSeerX 10.1.1.368.6137 (https://citeseerx.ist.psu.edu/viewdoc/
summary?doi=10.1.1.368.6137).
106. Go Authors. "Share Memory By Communicating" (https://go.dev/doc/codewalk/sharem
em/).
107. Cox, Russ. "Off to the Races" (http://research.swtch.com/gorace).
108. Pike, Rob (October 25, 2012). "Go at Google: Language Design in the Service of
Software Engineering" (https://talks.golang.org/2012/splash.article). Google, Inc.
"There is one important caveat: Go is not purely memory safe in the presence of
concurrency."
109. "Introducing the Go Race Detector" (https://go.dev/blog/race-detector). The Go Blog.
Retrieved June 26, 2013.
110. "Go 1.6 Release Notes - The Go Programming Language" (https://go.dev/doc/go1.6).
go.dev. Retrieved November 17, 2023.
111. "Frequently Asked Questions (FAQ) - the Go Programming Language" (https://golang.o
rg/doc/faq).
112. "A Story of a Fat Go Binary" (https://medium.com/@jondot/a-story-of-a-fat-go-binary-2
0edc6549b97). September 21, 2018.
113. "Go Programming Language Specification, §Interface types" (https://golang.org/ref/sp
ec#Interface_types). The Go Programming Language.
114. "Go Programming Language Specification, §Type assertions" (https://golang.org/ref/sp
ec#Type_assertion). The Go Programming Language.
115. "All Systems Are Go" (http://www.informit.com/articles/article.aspx?p=1623555).
informIT (Interview). August 17, 2010. Retrieved June 21, 2018.
116. "Language Design FAQ" (https://web.archive.org/web/20091113154906/http://golang.
org/doc/go_lang_faq.html#absent_features). November 13, 2009. Archived from the
original (https://golang.org/doc/go_lang_faq.html#absent_features) on November 13,
2009.
117. "Proposal for an exception-like mechanism" (https://groups.google.com/group/golang-
nuts/browse_thread/thread/1ce5cd050bb973e4). golang-nuts. March 25, 2010.
Retrieved March 25, 2010.
118. "Weekly Snapshot History" (https://golang.org/doc/devel/weekly.html#2010-03-30).
The Go Programming Language.
119. "Panic And Recover" (https://code.google.com/p/go-wiki/wiki/PanicAndRecover). Go
wiki.
120. "Effective Go" (https://golang.org/doc/effective_go.html#panic). The Go Programming
Language.

20 of 23 5/9/24, 21:14
Go (programming language) - Wikipedia https://en.wikipedia.org/wiki/Go_(programming_language)

121. "gofmt" (https://golang.org/cmd/gofmt/). The Go Programming Language. Retrieved

February 5, 2021.
122. "golang/lint public archive" (https://github.com/golang/lint). github.com. November 30,
2022.
123. "Effective Go" (https://golang.org/doc/effective_go.html). The Go Programming
Language.
124. "Unused local variables" (https://yourbasic.org/golang/unused-local-variables/).
yourbasic.org. Retrieved February 11, 2021.
125. "Unused package imports" (https://yourbasic.org/golang/unused-imports/).
yourbasic.org. Retrieved February 11, 2021.
126. "Code Review Comments" (https://github.com/golang/go/wiki/CodeReviewComments).
GitHub. Retrieved July 3, 2018.
127. "Talks" (https://talks.golang.org/). Retrieved July 3, 2018.
128. "Errors Are Values" (https://blog.golang.org/errors-are-values). Retrieved July 3, 2018.
129. "tools/gopls/README.md at master · golang/tools" (https://github.com/golang/tools/bl
ob/master/gopls/README.md). GitHub. Retrieved November 17, 2023.
130. "fmt" (https://golang.org/pkg/fmt/). The Go Programming Language. Retrieved April 8,
2019.
131. "testing" (https://golang.org/pkg/testing/). The Go Programming Language. Retrieved
December 27, 2020.
132. Lee, Wei-Meng (November 24, 2022). "Introduction to the Go Programming Language"
(https://web.archive.org/web/20230605071554/https://www.codemag.com/Article/201
1051/Introduction-to-the-Go-Programming-Language). Component Developer Magazine.
Archived from the original (https://www.codemag.com/Article/2011051/Introduction-to
-the-Go-Programming-Language) on June 5, 2023. Retrieved September 8, 2023.
133. Hoffmann, Frank; Neumeyer, Mandy (August 2018). "Simply Secure" (https://web.archiv
e.org/web/20230528175545/https://www.linux-magazine.com/Issues/2018/213/Caddy)
. Linux Magazine. No. 213. Archived from the original (https://www.linux-magazine.com
/Issues/2018/213/Caddy) on May 28, 2023. Retrieved September 8, 2023.
134. Lee, Wei-Meng (August 31, 2022). "Introduction to Containerization Using Docker" (htt
ps://www.codemag.com/Article/2103061/Introduction-to-Containerization-Using-Dock
er). CODE Magazine. Archived (https://web.archive.org/web/20230530073551/https://w
ww.codemag.com/Article/2103061/Introduction-to-Containerization-Using-Docker)
from the original on May 30, 2023. Retrieved September 8, 2023.
135. Pirker, Alexander (February 24, 2023). "Kubernetes Security for Starters" (https://www.c
odemag.com/Article/2303071/Kubernetes-Security-for-Starters). CODE Magazine.
Archived (https://web.archive.org/web/20230401212416/https://codemag.com/Article/
2303071/Kubernetes-Security-for-Starters) from the original on April 1, 2023. Retrieved
September 8, 2023.
136. Taft, Rebecca; Sharif, Irfan; Matei, Andrei; Van Benschoten, Nathan; Lewis, Jordan;
Grieger, Tobias; Niemi, Kai; Woods, Andy; Birzin, Anne; Poss, Raphael; Bardea, Paul;
Ranade, Amruta; Darnell, Ben; Gruneir, Bram; Jaffray, Justin; Zhang, Lucy; Mattis, Peter
(June 11, 2020). "CockroachDB: The Resilient Geo-Distributed SQL Database".
Proceedings of the 2020 ACM SIGMOD International Conference on Management of Data.
SIGMOD '20. pp. 1493–1509. doi:10.1145/3318464.3386134 (https://doi.org/10.1145%2
F3318464.3386134). ISBN 978-1-4503-6735-6.
137. Hopkins, Brandon (September 13, 2022). "Static Site Generation with Hugo" (https://w
ww.linuxjournal.com/content/static-site-generation-hugo). Linux Journal. Archived (http
s://web.archive.org/web/20230408065506/https://www.linuxjournal.com/content/stati
c-site-generation-hugo) from the original on April 8, 2023. Retrieved September 8,
2023.

21 of 23 5/9/24, 21:14
Go (programming language) - Wikipedia https://en.wikipedia.org/wiki/Go_(programming_language)

138. Simionato, Michele (November 15, 2009). "Interfaces vs Inheritance (or, watch out for
Go!)" (http://www.artima.com/weblogs/viewpost.jsp?thread=274019). artima. Retrieved
November 15, 2009.
139. Astels, Dave (November 9, 2009). "Ready, Set, Go!" (https://web.archive.org/web/20181
019164102/https://www.engineyard.com/blog/ready-set-go). engineyard. Archived
from the original (https://www.engineyard.com/blog/ready-set-go) on October 19,
2018. Retrieved November 9, 2009.
140. jt (January 11, 2010). "Google's Go Wins Programming Language Of The Year Award" (h
ttp://jaxenter.com/google-s-go-wins-programming-language-of-the-year-award-10069.
html). jaxenter. Retrieved December 5, 2012.
141. "TIOBE Programming Community Index for June 2015" (http://www.tiobe.com/index.p
hp/content/paperinfo/tpci/index.html). TIOBE Software. June 2015. Retrieved July 5,
2015.
142. Eckel, Bruce (August 27, 2011). "Calling Go from Python via JSON-RPC" (http://www.arti
ma.com/weblogs/viewpost.jsp?thread=333589). Retrieved August 29, 2011.
143. Hundt, Robert (2011). Loop recognition in C++/Java/Go/Scala (https://days2011.scala-lan
g.org/sites/days2011/files/ws3-1-Hundt.pdf) (PDF). Scala Days.
144. Metz, Cade (July 1, 2011). "Google Go strikes back with C++ bake-off" (https://www.ther
egister.co.uk/2011/07/01/go_v_cpluplus_redux/). The Register.
145. Yager, Will. "Why Go is not Good" (http://yager.io/programming/go.html). Retrieved
November 4, 2018.
146. Dobronszki, Janos. "Everyday Hassles in Go" (https://crufter.com/everyday-hassles-in-g
o). Retrieved November 4, 2018.
147. "Why are there braces but no semicolons? And why can't I put the opening brace on
the next line?" (https://golang.org/doc/faq#semicolons). Retrieved March 26, 2020.
"The advantages of a single, programmatically mandated format for all Go programs
greatly outweigh any perceived disadvantages of the particular style."
148. "I want off Mr. Golang's Wild Ride" (https://fasterthanli.me/articles/i-want-off-mr-golan
gs-wild-ride). February 28, 2020. Retrieved November 17, 2020.
149. "proposal: os: Create/Open/OpenFile() set FILE_SHARE_DELETE on windows #32088" (ht
tps://github.com/golang/go/issues/32088). GitHub. May 16, 2019. Retrieved
November 17, 2020.
150. Tu, Tengfei (2019). "Understanding Real-World Concurrency Bugs in Go" (https://songl
h.github.io/paper/go-study.pdf) (PDF). "For example, around 58% of blocking bugs are
caused by message passing. In addition to the violation of Go's channel usage rules
(e.g., waiting on a channel that no one sends data to or close), many concurrency bugs
are caused by the mixed usage of message passing and other new semantics and new
libraries in Go, which can easily be overlooked but hard to detect"
151. Brownlee, John (November 13, 2009). "Google didn't google "Go" before naming their
programming language' " (https://web.archive.org/web/20151208143907/http://www.g
eek.com/news/google-didnt-google-go-before-naming-their-programming-language-9
77351/). Archived from the original (http://www.geek.com/news/google-didnt-google-g
o-before-naming-their-programming-language-977351/) on December 8, 2015.
Retrieved May 26, 2016.
152. Claburn, Thomas (November 11, 2009). "Google 'Go' Name Brings Accusations Of Evil' "
(https://web.archive.org/web/20100722010320/http://www.informationweek.com/new
s/software/web_services/showArticle.jhtml?articleID=221601351). InformationWeek.
Archived from the original (http://www.informationweek.com/news/software/web_serv
ices/showArticle.jhtml?articleID=221601351) on July 22, 2010. Retrieved January 18,
2010.

22 of 23 5/9/24, 21:14
Go (programming language) - Wikipedia https://en.wikipedia.org/wiki/Go_(programming_language)

153. "Issue 9 - go — I have already used the name for *MY* programming language" (http
s://github.com/golang/go/issues/9#issuecomment-66047478). Github. Google Inc.
Retrieved October 12, 2010.

Further reading
▪ Donovan, Alan; Kernighan, Brian (October 2015). The Go Programming Language (http
s://www.informit.com/store/go-programming-language-9780134190440) (1st ed.).
Addison-Wesley Professional. p. 400. ISBN 978-0-13-419044-0.
▪ Bodner, Jon (March 2021). Learning Go (https://www.oreilly.com/library/view/learning-g
o/9781492077206/) (1st ed.). O'Reilly. p. 352. ISBN 9781492077213.

External links
▪ Official website (https://go.dev)

Retrieved from "https://en.wikipedia.org/w/index.php?title=Go_(programming_language)&

oldid=1222097598"

23 of 23 5/9/24, 21:14