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

29 lines
764 B
TOML

[package]
name = "air-trace-handler"
version = "0.1.0"
description = "Implementation of AIR trace handler"
authors = ["Fluence Labs"]
edition = "2018"
license = "Apache-2.0"
publish = false
keywords = ["fluence", "air", "webassembly", "programming-language"]
categories = ["wasm"]
[lib]
name = "air_trace_handler"
path = "src/lib.rs"
[dependencies]
air-interpreter-cid = { version = "0.2.0", path = "../interpreter-cid" }
air-interpreter-data = { path = "../interpreter-data" }
air-interpreter-interface = { path = "../interpreter-interface" }
air-log-targets = { path = "../log-targets" }
air-parser = { path = "../air-parser" }
polyplets = { path = "../polyplets" }
bimap = "0.6.2"
serde_json = "1.0.91"
log = "0.4.17"
thiserror = "1.0.38"
tracing = "0.1.37"