aquavm/crates/air-lib/trace-handler
Ivan Boldyrev 8f587b7803
feature(execution-engine): Canon data with CID (#419)
* Use CID values for tetraplets and `canon` vectors.

* Rename `cid_store` to `value_store`

It is consistent with the new `tetraplet_store` and `canon_store`
fields.

* Make canon data more typeful

The `CanonResult` doesn't take a JSON value anymore that is further
deserialized elsewhere, but is a struct that has all data deserialized.

* Typeful `CID` type

The `CID` type has a phantom type paramter defining its value's type.

* Group cid stores and trackers

Group cid stores into `CidInfo` struct, and trackers into `ExecutionCidState` struct.
2023-01-09 13:22:57 +07:00
..
src feature(execution-engine): Canon data with CID (#419) 2023-01-09 13:22:57 +07:00
.rustfmt.toml Decouple log targets to a separate crate (#152) 2021-10-05 16:55:04 +03:00
Cargo.toml feature(execution-engine): Canon data with CID (#419) 2023-01-09 13:22:57 +07:00
README.md Rename subtree to subgraph (#265) 2022-05-17 15:53:33 +03:00

AIR trace handler

This crate contains implementation of the CRDT-based merging data algorithm. It exposes the TraceHandler struct that based on the visitor pattern and has public methods that should be called in certain places of AIR instructions execution. Internally TraceHandler contains several FSM and each of such public methods does state transitioning of one or more these FSMs. Below are state transition sequences for all instructions that caller must follow.

Ap instruction

Expected sequence of TraceHandler calls for the ap instruction:

meet_ap_start
    -> meet_ap_end

Call instruction

Expected sequence of TraceHandler calls for the call instruction:

meet_call_start
    -> meet_call_end

Par instruction

Expected sequence of TraceHandler calls for the par instruction:

meet_par_start
    -> meet_par_subgraph_end(..., SubgraphType::Left)
    -> meet_par_subgraph_end(..., SubgraphType::Right)

Fold instruction

Expected sequence of TraceHandler calls for the fold instruction:

meet_fold_start.1 ->
    meet_generation_start.N ->
        meet_next.M ->
        meet_prev.M ->
    meet_generation_end.N ->
meet_fold_end.1

where .T means that this function should be called exactly T times.