Crates.io | ink-analyzer-ir |
lib.rs | ink-analyzer-ir |
version | 0.14.0 |
source | src |
created_at | 2023-04-14 14:52:03.807388 |
updated_at | 2024-05-03 15:49:28.602222 |
description | Intermediate representations (IRs) and abstractions of ink! smart contract code for ink! analyzer. |
homepage | https://github.com/ink-analyzer/ink-analyzer |
repository | https://github.com/ink-analyzer/ink-analyzer |
max_upload_size | |
id | 839209 |
size | 325,206 |
ink! intermediate representations (IRs) and abstractions for ink! analyzer.
This library implements types and abstractions for all ink! entities (e.g contracts, storage, events, topics, impls, constructors, messages, selectors, tests, trait definitions, chain extensions, storage items e.t.c).
It uses rust-analyzer's ra_ap_syntax crate for generating the syntax tree of the ink! smart contract code that it then converts into ink! entity intermediate representations and abstractions.
It uses ra_ap_syntax instead of other Rust parsing and syntax tree libraries because ink! analyzer has similar design goals to rust-analyzer. The most important being that parsing should be:
It's the main dependency for the semantic analyzer crate.
Run the following Cargo command in your project directory
cargo add ink-analyzer-ir
Generate an IR of ink! smart contract code.
use ink_analyzer_ir::InkFile;
fn generate_ir() {
let file = InkFile::parse(r#"
#[ink::contract]
mod my_contract {
#[ink(storage)]
pub struct MyContract {
value: bool,
}
// --snip--
}
"#);
dbg!(&file);
let contracts = file.contracts();
dbg!(&contracts);
if let Some(contract) = contracts.first() {
let storage = contract.storage();
dbg!(&storage);
}
}
https://docs.rs/ink-analyzer-ir/latest/ink_analyzer_ir/
Or you can access documentation locally by running the following command from the project root
cargo doc -p ink-analyzer-ir --open
You can run unit tests for all the core functionality by running the following command from the project root
cargo test -p ink-analyzer-ir
Licensed under either MIT or Apache-2.0 license at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.