implement PLN-0035 spec wording for materialization
This commit is contained in:
@@ -17,6 +17,17 @@ All runtime values are stored in VM slots as `Value`.
|
||||
| `bool` | Boolean value |
|
||||
| `float` | 64-bit floating point |
|
||||
|
||||
### String values
|
||||
|
||||
PROMETEU supports string values in the VM language surface.
|
||||
|
||||
String rules:
|
||||
|
||||
- hardcoded strings may be materialized once during build/load through constant-pool-backed storage;
|
||||
- runtime-created strings may materialize at the point where a new string value is semantically created;
|
||||
- the public value model does not require repeated payload copies after first materialization;
|
||||
- reducing repeated string copy pressure is an internal runtime concern and MUST NOT be interpreted as a guest-visible ABI distinction.
|
||||
|
||||
### Built-in vector and graphics types
|
||||
|
||||
These are treated as VM values with stable layout semantics.
|
||||
|
||||
@@ -27,6 +27,7 @@ The stack stores transient execution values and frame-scoped data.
|
||||
The stack may contain:
|
||||
|
||||
- primitive values;
|
||||
- string values;
|
||||
- built-in fixed-layout values;
|
||||
- heap handles;
|
||||
- tuple-shaped multi-return values.
|
||||
@@ -155,6 +156,15 @@ Heap allocation conceptually performs:
|
||||
2. create or reuse gate entry;
|
||||
3. return validated handle.
|
||||
|
||||
First materialization cost is distinct from repeated hot-path copy pressure.
|
||||
|
||||
Implications:
|
||||
|
||||
- constant-pool-backed values may pay materialization cost before execution begins;
|
||||
- runtime-created values may pay materialization cost when a new value is semantically produced;
|
||||
- the runtime SHOULD minimize repeated implicit copying on hot paths after that first materialization;
|
||||
- zero-allocation happy-path work is an engineering optimization target, not a published compatibility guarantee by itself.
|
||||
|
||||
If allocation fails:
|
||||
|
||||
- the VM may trigger GC;
|
||||
|
||||
@@ -188,6 +188,15 @@ Limit:32KB
|
||||
|
||||
These data feed host-owned certification.
|
||||
|
||||
The profiling boundary MUST distinguish public certification input from internal engineering evidence.
|
||||
|
||||
In particular:
|
||||
|
||||
- host-owned certification may consume stable runtime counters such as heap usage and GC-related pressure;
|
||||
- internal counters for allocation events or string materialization may exist to guide implementation work;
|
||||
- such internal counters MUST NOT be treated as a guest-visible certification promise unless a separate decision explicitly promotes them;
|
||||
- zero-allocation happy-path goals remain internal engineering targets unless promoted to a public certification contract.
|
||||
|
||||
### 7.1 Bank Occupancy Profiling
|
||||
|
||||
Bank occupancy diagnostics are slot-first.
|
||||
|
||||
Reference in New Issue
Block a user