Support delegatecall host binding - #339
Conversation
|
CI follow-up: I checked the failing run. The delegatecall coverage added by this PR passed in CI:
The red checks are from workspace-wide failures in pre-existing paths: clippy Local validation for this PR also passed: |
|
Pushed a CI follow-up in 7fb6e57. Locally verified:\n\n- cargo fmt --check\n- cargo clippy --all -- -D warnings\n- cargo build --examples --target wasm32-unknown-unknown --release\n- cargo test -p zinkc-filetests examples --release -- --nocapture\n- cargo test -p zinkc-filetests system::delegatecall --release -- --nocapture\n- cargo test --workspace --release --no-fail-fast\n- cargo test --workspace --release --examples --no-fail-fast\n\nThe delegatecall changes are unchanged; this follow-up addresses the workspace CI blockers that were preventing the PR checks from reaching the delegatecall coverage cleanly. |
|
thanks for the contribution! will take a look! |
Summary
zink::asm::evm::delegatecallhost binding for the EVMDELEGATECALLopcodeevm.delegatecalland compiles it through zinkcFixes #254.
Verification
cargo fmt --checkcargo build -p zink --example delegatecall --target wasm32-unknown-unknowncargo test -p zink --example delegatecall -- --nocapturecargo test -p zinkc-filetests system::delegatecall -- --nocapturegit diff --check