# Lane > Lane is a data-oriented systems language: explicit SoA/AoS layout, explicit SIMD, multithreading as keywords, and tests, benchmarks and coverage built into the compiler. One source for every ISA. Every page below is plain Markdown with no JavaScript needed. Every Lane example on the site comes from a program that the compiler's test suite builds or parses, and is checked against it when the site is built. Docs updated 2026-10-15. Compiler messages are plain lines, `path:line:col: error: message`, on standard error. ## What is Lane Lane is a compiled systems programming language for software where data layout and speed decide the result, such as game engines, game servers and databases. Data layout is part of the type, SIMD is explicit and written once for every instruction set, threads are in the language, and tests live in the declaration of the function they check. - Lane builds a million lines into a running executable in 225 ms on 16 threads (prototype, 2026-10-14); on one thread the in-memory build phases take 1,105 ms (2026-10-18), and the goal is under one second. - Lane is a data-oriented programming language: SoA and AoS are keywords on array types, so the layout is part of the type, and lean packed types keep data compact. - Lane is a SIMD programming language with one source for every ISA: vec loops must vectorize at the target's native width or the build fails, per-ISA code is chosen with when, and the targets include x86-64, AArch64, WebAssembly, RISC-V and SPIR-V. - Lane is a programming language with built-in tests and contracts: a test is one line in the function's declaration, about 8 tokens, and the compiler runs it during the build; an estimate puts the saving at about 25% fewer tokens for well-tested code (2026-10-14). - Lane is a systems programming language for game engines: data layout is part of the type, threads are in the language with access modes that make conflicts checkable, and struct-of-arrays data fits the entity-component pattern. ## Status (as of 2026-10-22) Which constructs the current compiler accepts. The language is larger than this list; see the roadmap for what comes next. - **Builds:** integers and bool, f32 and f64 (strict IEEE, with a native square root), pointers, slices, arrays, records, enums, match, constants, functions, access modes (wr, out) and their aliasing check, if, for (all three forms), brk, nxt, ret, defer, use, pub, ext with @lib, embed, size_of, align_of, cast, slice, implicit conversions between number types when nothing can be lost, fixed-width vector types and their operations, contracts (assume lines and test examples, run during builds for every target, with exact float results and examples on exported library functions), and the standard library modules io, fmt, mem, os, bufio and float, plus files and processes on Windows. Constants that divide an integer by zero, or that are infinity or NaN, are compile-time errors. - **Parsed only:** vec and par, soa and aos, when, union, generics ($T), functions as values, variadic parameters, several results, attributes other than @lib, and test and bench blocks. The compiler refuses them with a "not supported ... yet" error. - **Not accepted:** record and array literals, returning a record or an array, and the number types f16, un8, un16, sn8, sn16, bf16, f8e4m3 and f8e5m2. - **Targets:** x86-64 Windows executables, x86-64 Linux executables (--target linux, static, no C library), wasm32 and wasm64 modules, AArch64 Linux and macOS (arm64) executables, and RISC-V 64 Linux executables. These describe the development compiler on 2026-10-22; the latest published release may predate some of them, and the Downloads page offers the latest published release. Optimization at -O1 is available on x86-64, AArch64 and RISC-V 64, and floats are optimized on x86-64. - **Compiler:** The compiler is written in Lane and builds itself to a byte-identical result (the fixpoint), on Windows, Linux and macOS (arm64); a bootstrap compiler only starts the chain. ## Start here - [Lane for agents](https://lane.trisgram.com/docs/agents.md): How to read and write Lane from a program: the index files, the one-page cheat sheet, verified examples and the error reference. - [Lane in one page](https://lane.trisgram.com/docs/agents/lane-in-one-page.md): Every construct with one minimal example, and the exact rules an agent gets wrong without them. ## Language documentation - [Lane documentation](https://lane.trisgram.com/docs.md): A syntax tour of Lane for people, and a set of plain-Markdown pages for agents. - [Types and literals](https://lane.trisgram.com/docs/types.md): Scalar types, wrapping arithmetic, literals that take their type from context, and why nothing converts implicitly. - [Declarations and functions](https://lane.trisgram.com/docs/declarations.md): Type-first declarations, functions, the access modes wr and out that are repeated at the call, several results, variadic parameters and function types. - [Statements and control flow](https://lane.trisgram.com/docs/statements.md): Semicolons, scopes without shadowing, if, the three kinds of for, brk, nxt, ret, defer and the check that every path returns. - [Records, enums and match](https://lane.trisgram.com/docs/records-enums.md): C-layout records, copying and modes, enums stored as u32, unchecked conversion, and match with exhaustiveness. - [Constants](https://lane.trisgram.com/docs/constants.md): NAME :: expr; constants, exact compile-time arithmetic on 128 bits, typed and untyped constants, and dependency order. - [Memory](https://lane.trisgram.com/docs/memory.md): Arrays, slices, pointers, cast and slice, and arenas. There is no new, no global heap and no destructor. - [Data layout, SIMD and threads](https://lane.trisgram.com/docs/layout-simd.md): soa and aos as part of the type, vector values against arrays in memory, vec loops that must vectorize, and par. - [Per-ISA code, hints and floats](https://lane.trisgram.com/docs/targets-hints.md): when selects declarations per target at compile time, optimizer hints are predeclared functions and attributes, and float code is strict unless a function relaxes it with @fp. - [Contracts and tests](https://lane.trisgram.com/docs/contracts.md): Functions that state what they require with assume and what they return with examples, test and bench blocks, and the report format. - [Modules and the standard library](https://lane.trisgram.com/docs/modules.md): One file is one module. use, pub, ext and @lib, and what io, fmt, mem, os and bufio contain. - [The lane command and its tests](https://lane.trisgram.com/docs/tooling.md): lane lex, parse and build; exit codes and diagnostics; and how the examples on this site are verified. ## Examples and errors - [Verified examples](https://lane.trisgram.com/docs/agents/examples.md): Programs from the Lane test suite with their expected standard output and exit codes, grouped by feature. - [Error reference](https://lane.trisgram.com/docs/agents/errors.md): Every distinct compiler message that the test suite checks, with a program that triggers it. ## Project - [Targets](https://lane.trisgram.com/targets.md): Which instruction sets and operating systems Lane builds for, their executable formats, SIMD and how parity is tested. - [Roadmap](https://lane.trisgram.com/roadmap.md): The planned order of work on Lane, with the state of each item. - [Measurements](https://lane.trisgram.com/measurements.md): Every number on this site and how it was measured, and how Lane compiles itself. - [Downloads](https://lane.trisgram.com/downloads.md): The Lane compiler and programs written in Lane: Lane Notepad (text editor), ImgLane (image viewer and converter), LaneMonitor (resource monitor) and CommandLane (command-line replacement); plus the Aurelium browser. Each comes with its SHA-256 checksum. - [Lane Explorer](https://lane.trisgram.com/explorer.md): Write Lane as text or as a node graph and see the code generated for each instruction set, with the compiler running in your browser. - [Use cases](https://lane.trisgram.com/use-cases.md): The tools and showcases Lane is designed to include, each linked to its item on the roadmap. ## Optional - [The whole reference in one file](https://lane.trisgram.com/llms-full.txt): every page above in one plain-text file, except the verified examples (linked above) and the downloads page. It includes the one-page cheat sheet, the error reference, the targets, the roadmap, the measurements and the use cases.