aboutsummaryrefslogtreecommitdiffstats
path: root/docs/design
Commit message (Collapse)AuthorAgeFilesLines
...
* Document the text language as implementedeunhhu2026-09-252-2/+18
| | | | | | | Record v0b as complete: which text syntax exists, what is still missing (multi-line strings, formats, graphemes, words), the insertion rule for cursors, and how the text model and parity checks verify it.
* Compile messages and keyed documents to module v2eunhhu2026-09-252-17/+24
| | | | | | | | | | | | | | | | | | aup now emits Pure module v2 and adds keyed byte collections (state documents: bytes by key), message inputs by key with u32 and a trailing bytes field, on-message handlers, field access, name[key] reads and .bytes sizes, replace(a .. b, value), reply and require, all checked for number/bytes types with file:line:column diagnostics. The document editor and its size-bounded variant are rewritten in aup. make check runs them through pure-edit-module against pure-edit running the original editor.pure programs: 1,280 random show/edit/apply operations, including conflicts, limits, missing documents, budgets and invalid keys, produce byte-identical stdout, stderr and exit codes, and each CLI reads the other's store identically. v0a parity with the workbench engine, 33 diagnostics and generated/damaged programs still pass, also with a sanitizer-built compiler.
* Set the DSL direction and the text modeleunhhu2026-09-251-0/+70
| | | | | | | | | | aup declares connections and leaves storage, transactions and screen models to Pure. Interface vocabulary lives in Vega, an aup library, not in the language. text is one immutable UTF-8 type from a word to a 1 MiB document; positions are cursors bound to a value that stay on character boundaries and follow edits, lengths name their unit, and comparison is exact without silent normalization. Stages v0b-v0d and their acceptance tests are listed.
* Charter aup and specify language v0eunhhu2026-09-251-0/+110
aup is the language and toolchain for the Pure runtime, as Java and javac are for the JVM. v0a unifies the workbench scalar dialect (state, key inputs, atomic handlers, views) with the same numeric semantics; v0b drafts byte values and runtime-owned persistent documents to replace the document dialect. Parity with the existing executors is the acceptance test.