What's new:
- NaN-boxing — All stack values are 64-bit (u64) encoding 6 distinct types (Null, Boolean(TRUE_VAL,FALSE_VAL), STRING_VAL, CALLDATA_VAL, U32_VAL, MEM_SLICE_VAL (offset: 25 bits, size: 25 bits)).
- InlineVec — Fixed-size array-backed vector implementation used for stack, control stack, call stack, and jump stack with specified limits.
- Dynamic Memory/Heap — growable Vec heap; memory slices use 25-bit offset and 25-bit size fields (limited by MEM_SLICE_VAL).
- Zero dependencies —Custom binary encoding/decoding implementation.
Furthermore I added an example to stresstest VM - a todo app with programmable tasks.
In this example, all todo operations — from simple CRUD to tasks own instructions — are executed by a virtual machine.
The concept is that any kind of automation or workflow can be enabled by task instructions executed by the VM, rather than hardcoded functions in the app. It’s close to the concept of rules engines.
There are 4 demo task instructions:
- chain - Creates next task once when another completes. Removes calldata after call - called once
- either - Sets complete if either one or another task is completed + deletes not completed task (see gif)
- destructable - task self destructs when it’s status set to complete
- hide - Keeps task hidden while specified task’s status is not complete.
It is possible to add your own instructions to calldata.toml and use them within todo example:
cargo run -- add <TASK_TITLE > -calldata <INSTRUCTION_NAME> <PARAMETERS>
todo example : https://github.com/tracyspacy/spacydo/tree/main/examples/todo
vm repo: https://github.com/tracyspacy/spacydo