Package treego implements a generic B-tree data structure in Go.
Package gographviz provides parsing for the DOT grammar into an abstract syntax tree representing a graph, analysis of the abstract syntax tree into a more usable structure, and writing back of this structure into the DOT format.
Package kdtree implements a k-d tree data structure.
Package encoding provides a few of the encoding structures that are missing from the Go x/text/encoding tree.
Package srcdom provides utilities to manipulate Go's AST (Abstract Structure Tree).
Package btree implements in-memory B-Trees of arbitrary degree. btree implements an in-memory B-Tree for use as an ordered data structure. It is not meant for persistent storage solutions. It has a flatter structure than an equivalent red-black or other binary tree, which in some cases yields better memory usage and/or performance. See some discussion on the matter here: Note, though, that this project is in no way related to the C++ B-Tree implementation written about there. Within this tree, each node contains a slice of items and a (possibly nil) slice of children. For basic numeric values or raw structs, this can cause efficiency differences when compared to equivalent C++ template code that stores values in arrays within the node: These issues don't tend to matter, though, when working with strings or other heap-allocated structures, since C++-equivalent structures also must store pointers and also distribute their values across the heap. This implementation is designed to be a drop-in replacement to gollrb.LLRB trees, (http://github.com/petar/gollrb), an excellent and probably the most widely used ordered tree implementation in the Go ecosystem currently. Its functions, therefore, exactly mirror those of llrb.LLRB where possible. Unlike gollrb, though, we currently don't support storing multiple equivalent values.
Package ki provides the top-level repository for GoKi Trees: Ki = Tree in Japanese, and "Key" in English -- powerful tree structures supporting scenegraphs, programs, parsing, etc.
Package ogdl is used to process OGDL, the Ordered Graph Data Language. OGDL is a textual format to write trees or graphs of text, where indentation and spaces define the structure. Here is an example: The languange is simple, either in its textual representation or its number of productions (the specification rules), allowing for compact implementations. OGDL character streams are normally formed by Unicode characters, and encoded as UTF-8 strings, but any encoding that is ASCII transparent is compatible with the specification. See the full spec at http://ogdl.org. To install this package just do: If we have a text file 'config.ogdl' containing: then, will print If the timeout parameter was not present, then the default value (60) will be assigned to 'to'. The default value is optional, but be aware that Int64() will return 0 in case that the parameter doesn't exist. The configuration file can be written in a conciser way: The package includes a template processor. It takes an arbitrary input stream with some variables in it, and produces an output stream with the variables resolved out of a Graph object which acts as context. For example (given the previous config file): string(b) is then: Some rules are followed:
Package template is muxt's template engine: a text/template parser that records source positions and parses HTML structure, and the execution engine for its trees.
Package gographviz provides parsing for the DOT grammar into an abstract syntax tree representing a graph, analysis of the abstract syntax tree into a more usable structure, and writing back of this structure into the DOT format.
Package taxonomykit builds validated, deterministic, localized taxonomy trees from a flat list of nodes and answers the structural questions applications ask of them: lineage, children, siblings, leaves, breadcrumbs and slug lookup.
Package actTree implements a double-linked tree data structure.
Package tbsconv converts between the TBSCertificate structure of RFC 5280 and the TBSCertificateLogEntry structure of Merkle Tree Certificates (draft-ietf-plants-merkle-tree-certs).
Package strata is an embedded, ordered key-value store built as a log-structured merge tree on the Go standard library alone.
Package gographviz provides parsing for the DOT grammar into an abstract syntax tree representing a graph, analysis of the abstract syntax tree into a more usable structure, and writing back of this structure into the DOT format.
The trie package implements a trie (prefix tree) data structure over byte slices.
Package lifecycle provides structured concurrency and resource lifetimes: a tree of scopes that own goroutines, io.Closers and child scopes, a bounded queue with an explicit policy for when it is full, and newest-value-wins mailboxes (Latest, KeyedLatest).
Package irac defines the formal schema for the Issue-Rule-Application- Conclusion (IRAC) reasoning tree: the structural backbone every later reasoning phase (033-062) builds on.
Package juuri is a persistent (immutable, structurally shared), path-compressed radix tree with watch channels: the storage engine of go-maemmidb, as a library.
Package gographviz provides parsing for the DOT grammar into an abstract syntax tree representing a graph, analysis of the abstract syntax tree into a more usable structure, and writing back of this structure into the DOT format.
Package agentsession implements the Agent Session Format: an append-only, tree-structured JSONL record of one agent session whose conversation payloads are Open Responses items.
Package keelstore implements an embedded, crash-safe, log-structured merge-tree (LSM) key/value store in pure Go, with no third-party dependencies.
Package lsmdb is an embedded key-value store built on a log-structured merge-tree.
Package ki provides the base element of Goki Trees: Ki = Tree in Japanese, and "Key" in English -- powerful tree structures supporting scenegraphs, programs, parsing, etc.
Package gographviz provides parsing for the DOT grammar into an abstract syntax tree representing a graph, analysis of the abstract syntax tree into a more usable structure, and writing back of this structure into the DOT format.
Package trace records the call tree of a program for inspection and printing -- think structured function-entry / function-exit logging with optional inline messages.
Package gographviz provides parsing for the DOT grammar into an abstract syntax tree representing a graph, analysis of the abstract syntax tree into a more usable structure, and writing back of this structure into the DOT format.
Package gographviz provides parsing for the DOT grammar into an abstract syntax tree representing a graph, analysis of the abstract syntax tree into a more usable structure, and writing back of this structure into the DOT format.
Package treeview provides a flexible tree structure for building interactive terminal user interfaces.
Package fractaltree provides an in-memory B-epsilon-tree (fractal tree), a write-optimized ordered key-value data structure.
Package build gathers information about Go packages. A build constraint, also known as a build tag, is a condition under which a file should be included in the package. Build constraints are given by a line comment that begins Build constraints may also be part of a file's name (for example, source_windows.go will only be included if the target operating system is windows). See 'go help buildconstraint' (https://pkg.go.dev/cmd/go#hdr-Build_constraints) for details. The Go path is a list of directory trees containing Go source code. It is consulted to resolve imports that cannot be found in the standard Go tree. The default path is the value of the GOPATH environment variable, interpreted as a path list appropriate to the operating system (on Unix, the variable is a colon-separated string; on Windows, a semicolon-separated string; on Plan 9, a list). Each directory listed in the Go path must have a prescribed structure: The src/ directory holds source code. The path below 'src' determines the import path or executable name. The pkg/ directory holds installed package objects. As in the Go tree, each target operating system and architecture pair has its own subdirectory of pkg (pkg/GOOS_GOARCH). If DIR is a directory listed in the Go path, a package with source in DIR/src/foo/bar can be imported as "foo/bar" and has its compiled form installed to "DIR/pkg/GOOS_GOARCH/foo/bar.a" (or, for gccgo, "DIR/pkg/gccgo/foo/libbar.a"). The bin/ directory holds compiled commands. Each command is named for its source directory, but only using the final element, not the entire path. That is, the command with source in DIR/src/foo/quux is installed into DIR/bin/quux, not DIR/bin/foo/quux. The foo/ is stripped so that you can add DIR/bin to your PATH to get at the installed commands. Here's an example directory layout: In Go 1.12 and earlier, it was possible to distribute packages in binary form without including the source code used for compiling the package. The package was distributed with a source file not excluded by build constraints and containing a "//go:binary-only-package" comment. Like a build constraint, this comment appeared at the top of a file, preceded only by blank lines and other line comments and with a blank line following the comment, to separate it from the package documentation. Unlike build constraints, this comment is only recognized in non-test Go source files. The minimal source code for a binary-only package was therefore: The source code could include additional Go code. That code was never compiled but would be processed by tools like godoc and might be useful as end-user documentation. "go build" and other commands no longer support binary-only-packages. Import and ImportDir will still set the BinaryOnly flag in packages containing these comments for use in tools and error messages.
Package treeview provides a flexible tree structure for building interactive terminal user interfaces.
Package tree provides a simple structure for dealing with dynamic or unknown JSON/YAML structures.
Package gander implements a tree zipper: a functional, immutable cursor for navigating and editing arbitrary tree structures.
Package errortree provides primitives for working with errors in tree structure errortree is intended to be used in places where errors are generated from an arbitrary tree structure, like the validation of a configuration file.
Package langdag provides a Go library for managing AI agent conversations with tree-structured storage and multi-provider LLM routing.
Package teatree provides a generic Bubble Tea v2 component for rendering and navigating expandable/collapsible tree structures.
Package gographviz provides parsing for the DOT grammar into an abstract syntax tree representing a graph, analysis of the abstract syntax tree into a more usable structure, and writing back of this structure into the DOT format.