This package provides an in-memory B-Tree implementation for Go, useful as an ordered, mutable data structure.

This package provides a machine architecture information used by the Go toolchain. The parts needed in the main Go repository are copied in.

This package provides a markdown parser.

This repository holds the Go Telemetry server code and libraries, used for hosting telemetry.go.dev and instrumenting Go toolchain programs with opt-in telemetry.

This package provides supplemental libraries offering Go support for low-level interaction with the operating system.

This package provides supplementary cryptographic libraries for the Go language.

This package provides Go concurrency primitives in addition to the ones provided by the language and sync and sync/atomic packages. The package provides several Golang submodules:

• errgroup - synchronization, error propagation, and Context cancellation for groups of goroutines working on subtasks of a common task

• semaphore - a weighted semaphore implementation

• singleflight - a duplicate function call suppression mechanism

• syncmap - a concurrent map implementation

This repository holds packages for writing tools that work directly with Go module mechanics. That is, it is for direct manipulation of Go modules themselves.

The specific case of loading packages should still be done by invoking the go command, which remains the single point of truth for package loading algorithms.

This package provides supplemental Go libraries for text processing.

This package provides most of the code for running a godoc server.

This package provides supplementary cryptographic libraries for the Go language.

The avo package presents a familiar assembly-like interface that simplifies development without sacrificing performance.

Package pdf implements reading of PDF files.

This package provides supplemental Go networking libraries.

The Common Expression Language (CEL) implements common semantics for expression evaluation, enabling different applications to more easily interoperate.

This subrepository holds experimental and deprecated (in the old directory) packages.

The uuid package generates and inspects UUIDs based on RFC 4122 and DCE 1.1: Authentication and Security Services.

This package provides a rpc Google's API gRPC type derived from google.golang.org/protobuf.

This package is intended to be a more powerful and safer alternative to reflect.DeepEqual for comparing whether two values are semantically equal.

The config package holds the config.json file defining the Go telemetry upload configuration and contains no actual Go code, and exists only so the config.json file can be served by module proxies.

An upload configuration specifies the set of values that are permitted in telemetry uploads: GOOS, GOARCH, Go version, and per-program counters.

Gocc is a compiler kit for Go written in Go. Gocc generates lexers and parsers or stand-alone DFAs or parsers from a BNF. Lexers are DFAs, which recognise regular languages. Gocc lexers accept UTF-8 input. Gocc parsers are PDAs, which recognise LR-1 languages. Optional LR1 conflict handling automatically resolves shift / reduce and reduce / reduce conflicts.

This package provides a library for calling C functions from Go without Cgo.

Featues:

• build for other platforms easily without a C compiler

• efficiently cache entirely Go builds

• using Cgo generates a C wrapper function for each C function called

• load symbols at runtime and use it as a plugin system

• call into other languages that are compiled into shared objects

• works even with CGO_ENABLED=1 so incremental porting is possible

The cmdtest package simplifies testing of command-line interfaces. It provides a simple, cross-platform, shell-like language to express command execution. It can compare actual output with the expected output, and can also update a file with new "golden" output that is deemed correct.

This repository holds packages for writing tools that work directly with Go module mechanics. That is, it is for direct manipulation of Go modules themselves.

The specific case of loading packages should still be done by invoking the go command, which remains the single point of truth for package loading algorithms.