Skip to content

Instantiation, records, traits and scheduling

Y constructs a named value from Props; HY emits a struct-shaped record declaration from Props. Empty or omitted Props preserve braces: Key {} and struct Key {} respectively. They do not silently become unit structs. Nonempty fields retain their supplied order, names and native types/values.

Empty HY accepts absent Shape or Record; Sum rejects. Empty HY/MY collections cannot accompany composed member/header children the wrappers would discard. These guards do not establish composed field/method implementations, enums or sum types. KY invocation is described with callables.

The empty-instantiations witness covers omitted/explicit-empty records, construction, populated controls and traits. Five stored malformed inputs exercise unsupported combinations. Instantiation, Instantiate and empty validation own this implementation boundary.

MY emits receiverless required trait signatures from ordered Funcs. Each signature has a native name and named/typed inputs. Missing or empty Outputs omit the return annotation; supplied outputs retain their punctuation and terminating semicolon. Nested native type commas are decoded by the existing record machinery.

Any supplied Receiver field rejects, including empty Receiver. Trait-level Lifetimes/GenericTypes qualify the trait once, not each method. Default/composed methods, separate method parameter lists and implementation blocks remain outside the supported contract. Empty Funcs emit trait Key {}.

The trait-signature witness includes native names/types spelled Void and eight required signatures. Native compilation checks declarations and type syntax; it executes no trait behavior.

V schedules native Key invocation text; MV schedules one Instantiation child through tokio::spawn. Both require an existing suitable future. The direct and composed witnesses are compile-only. App processes retain their own lifecycle.

CV constructs an unscheduled future from one W body: local Capture is Infer by default or Move. DV awaits one local Key or composed E/KY/CV/DV operand inside an asynchronous body. CO assigns its value; COB declares and initializes it. Rust checks borrowing, mutability and result types. See the complete future contract and composed executable witness.

Rust Execute/Execution exclude Deferred from inputs, forwarding and rendering. Supplying Deferred is unsupported even when its value is False. There is no deferred-call or destructor/RAII cleanup contract inferred from V/MV. Four malformed cases and scheduling tests preserve this rejection.

Read Execution, Execute, and execution without Deferred. Runtime launch, Stop, Await and cleanup belong to the CLI/runtime contract, not these scheduling templates.