Skip to content

Reading Guide

The Rethon Language Specification is structured so readers can move from identity and source form toward semantics, libraries, packaging, and tooling.

Start with Volume 01: Language Philosophy. It defines the language's identity: Python-inspired readability, static typing, AOT compilation, memory safety by default, value-oriented design, protocol-oriented abstraction, and explicit non-goals.

Then read Volume 02: Lexical Structure and Volume 03: Type System. These volumes establish source text, indentation, identifiers, literals, static typing, nullability, value and reference types, protocols, generics, and type compatibility.

After that, follow the topic area relevant to your work:

  • Compiler and tooling work: Volumes 02, 03, 04, 10, 13, 16, 18, 19, and 20.
  • Library and API design: Volumes 03, 05, 06, 07, 08, 09, 11, 15, and 17.
  • Application language semantics: Volumes 04 through 16.
  • Package and build workflows: Volumes 10, 18, 19, and 20.

Specification Conventions

The volumes use words such as "shall", "shall not", "may", and "should" deliberately:

  • "Shall" and "shall not" define normative requirements.
  • "May" allows implementation or tooling flexibility.
  • "Should" expresses a strong recommendation that supports the language's design goals.

Examples are illustrative unless a surrounding rule states that the exact form is required.

Public Site Scope

This site publishes the language specification. It is not a tutorial, implementation guide, package registry, or compiler manual. Those documents may reference this specification, but the source-level language contract lives here.