iolanguage.org valid

Io

A small, prototype-based programming language — now targeting WASM/WASI.

For agents: Io is a small prototype-based programming language targeting WASM/WASI, with a book, language reference, grammar and concurrency documentation.

io languageprototype-basedprogramming languagewasmconcurrencylanguage reference

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T17:49:20.292Z. Cached copy · Source on iolanguage.org

# Io

> A small, prototype-based programming language — now targeting WASM/WASI.

## Documentation

- [Documentation](/docs/): Guides, tutorial, language reference, and design notes.
- [Book](/docs/Book/): The original Io book, organized by chapter.
- [Appendix](/docs/Book/Appendix/): Grammar reference and citations.
- [Concurrency](/docs/Book/Concurrency/): Coroutines, actors, futures, and Io's concurrency model.
- [Control Flow](/docs/Book/Control%20Flow/): Branching, loops, exceptions, and scope.
- [Introduction](/docs/Book/Introduction/): The origins, philosophy, and influences behind Io.
- [Objects](/docs/Book/Objects/): Slots, prototypes, cloning, and differential inheritance.
- [Primitives](/docs/Book/Primitives/): Built-in objects: numbers, strings, lists, maps, files, and more.
- [Syntax](/docs/Book/Syntax/): Io's minimal grammar: expressions, messages, and operators.
- [Guide](/docs/Guide/): Comprehensive language guide: syntax, messages, objects, control flow, concurrency, and more.
- [Implementation](/docs/Implementation/): How the Io VM is put together, and how to extend it from C.
- [How to Write C Bindings](/docs/Implementation/How%20to%20Write%20C%20Bindings/): How to write Io-visible primitives in C — the macros, the argument-extraction API, proto registration, and GC-safe slot updates.
- [Overview](/docs/Implementation/Overview/): A tour of the Io VM source tree — object representation, the message tree, the evaluator, the standard library loader, and the garbage collector.
- [Reference](/docs/Implementation/Reference/): C-internal implementation details extracted from cdoc and cmetadoc comments.
- [BigInt](/docs/Implementation/Reference/BigInt/): C implementation of arbitrary-precision integers. Each BigInt is an IoObject whose dataPointer is an IoBigIntData that owns a libtommath mp_int (variable-size digit array on the heap). Unlike Number, BigInt has a real payload: rawClone allocates and mp_init's a fresh mp_int, and the tag's freeFunc must call mp_clear before freeing the wrapper. Operands must both be BigInts — there is no silent coercion from Number (matching JavaScript's BigInt rules), which is enforced by the IoBigInt_argData helper that raises an error on non-BigInt args. Every arithmetic method follows the same mp_init/op/mp_copy-into-new- BigInt/mp_clear pattern to keep libtommath's ownership discipline correct even in the face of GC-driven allocation.
- [Block](/docs/Implementation/Reference/Block/): C implementation of Io blocks and methods (they share the same struct; block() binds a lexical scope, method() leaves scope NULL so activation uses the message target). IoBlockData carries the message tree, an argNames List, the optional captured scope, passStops (whether return/continue/break propagate to the caller), and profiler timing. Activation happens via IoBlock_activate, which is installed as the tag's activateFunc — any getSlot of an activatable Block thus runs the block without explicit message dispatch. IoB
…

Related sites

Other listed sites in Developer tools. See the whole category →

Machine-readable: GET /v1/resolve?q=iolanguage.org · GET /v1/domain/iolanguage.org · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for iolanguage.org:
1. POST https://agentwebmap.com/v1/sites/iolanguage.org/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://iolanguage.org/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/iolanguage.org/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/iolanguage.org).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.