aup - Declarative systems language and compiler targeting verified Pure modules.

	Commit message (Collapse)	Author	Age	Files	Lines
*	Pure 027's 4f-4: a source of any size (files and standard input read whole), ↵	eunhhu	40 hours	1	-8/+19
\| \| \| \|	the compiler's tables raised to Pure's widths (4,096 states, 1,024 inputs, 4,096 views and handlers, 1,024 records, 16,384 record fields; 15 MB calloc'd, its unused rooms never touched) and its diagnostics saying so; at most 255 outputs (Pure's store counts them in a byte), a walked or folded list among the first 256 states (its argument's byte), said before Pure would refuse; a wide program checked: 301 states, 40 inputs, 70 views and 20 records in 48 KB of source, run to the last of each
*	Compile a query against an app (aup query)	eunhhu	2026-09-28	1	-11/+58
\| \| \| \| \| \| \| \|	aup query APP QUERY -o OUT compiles APP's declarations (records, states, inputs, handlers) with the views QUERY adds, as one module: the node checks that its states are the app's and runs the query's view on a snapshot of the app (PUT and GET /queries/NAME in pure-serve). QUERY may be - for standard input.
*	Name aup's one part: compiler/	eunhhu	2026-09-27	1	-0/+170
	As in Pure and Vega, the top level directories are the parts; aup has one, the compiler, checked end to end by tests/check.py.