Qu

Documentation

The reference describes what the engine does. Where the specification runs ahead of it, the builtin index is the authority.

Reference

Authoritative

Builtin index

All 777 function names, generated from the interpreter's own table. If a name is not here, the engine does not have it. Each one links to its own page, with worked examples and the output the engine actually produced.

Open →

By subject

Standard library

Core maths and linear algebra, signal processing, statistics and ML, plotting, images, collections, file I/O, concurrency.

Open →

Normative

Language specification

The language as designed. Ahead of the engine in places, and says so.

Open →

Getting started

Start Here

Open →

From Zero

Open →

Quickstart

Open →

Fundamentals

Open →

Numerics, DSP & Linear Algebra

Open →

Specialized Domains

Open →

Standard library

Standard Library

Open →

Builtin Index

Open →

Core Maths & Linear Algebra

Open →

Signal Processing

Open →

Compressed Sensing

Open →

Noise & Distortion

Open →

Statistics & ML

Open →

Plotting

Open →

Images

Open →

Collections & Strings

Open →

File I/O

Open →

Concurrency

Open →

REPL & Diagnostics

Open →

Reference

Agent Guide

Open →

Language Tour

Open →

Language Specification

Open →

What the language has

AreaWhat is in it
NumericsReal and complex scalars, vectors and matrices. FFT, filter design and application, resampling, windows, spectral estimates.
Linear algebraLU, QR, SVD, Cholesky, eigen, pseudo-inverse, least squares, condition number — on real and complex matrices. nnls and bounded nonlinear least_squares.
PlottingSVG, PDF with embedded subset fonts, TikZ. Maths in labels, twin axes with independent scales, contours, error bars, colorbars, 37 marker glyphs.
DataMATLAB .mat, CSV with provenance headers, raw binary arrays and structs, images, tables.
Statistics & MLSVM, random forests, gradient boosting, k-NN, PCA, GMM, MLPs, cross-validation, scalers, metrics.
SystemsParallel pmap and pools, GPU matmul, serial and TCP I/O, watches, sandboxing.

How the documentation is kept true

Two mechanisms, both mechanical, because prose about code drifts.

Generated

The index comes from the source

tools/gen_builtin_index.qu reads the interpreter's own name table, so the reference cannot claim a function that does not exist, or omit one that does.

Executed

Every example is run

tools/check_docs.sh extracts each code block and runs it, cumulatively per page, and reports how far a reader gets before it breaks.