Orkuncakilkaya
9452557f3c
A self-describing Value node (null/int/fixed/bool/str/list/object) with constructors, builders (Value.add/put) and accessors (get/at/count/kind/ as_int/as_str/…). Reflect.serialize(entity) walks an entity's whole component set into a value tree — one member per component, each a sub-object of its fields — and Reflect.apply(entity, value) writes one back; a fixed field becomes a fixed node, everything else an int node, so the round-trip is bit-exact, with the model id under "@kind". Json.encode/parse bridge the tree to and from compact, stable, diffable text, with fixed written as an exact terminating decimal that parses back bit-for-bit (verified across the raw Q16.16 range). Together: a one-call, bit-exact save/load for entities. Written in Ludic and spliced on demand (runtime/native/value.ludic + reflect_io.ludic, like Query/Light), so a program that doesn't touch Value.*/Json.*/Reflect.serialize compiles byte-identically and the C-free bootstrap fixpoint holds (verified). The general tagged-union/any language type stays tracked in #1; this ships the concrete value tree the serializer needs. Adds 21 namespace-method docs pages + Value/Json sections, examples/library/serialize.ludic, and a regression case. Whole CI set green: x test 72/72, x test-tools 30/30, check-impl/vocabulary/docs. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
990 B
990 B
| id | name | category | kind | tokens | sig | tip | order | ns | member |
|---|---|---|---|---|---|---|---|---|---|
| reflect-serialize | Reflect.serialize | reflect | namespace-method | Reflect.serialize | Reflect.serialize(entity) -> value | Walk an entity's components into a value tree. | 13 | Reflect | serialize |
Walks every component the entity carries and every field of each into a generic object value tree: one member per component, each a sub-object of its fields. A fixed field becomes a fixed node, everything else an int node, so a serialize → apply round-trip is bit-exact; the model id rides along under the reserved "@kind" key. Pair it with Json.encode for a one-call save. It names no component or field, so it works over any schema — the pattern auto-save and debug inspectors use.