feat(blockifier): add NativeSyscallHandler
#549
Conversation
# Conflicts: # crates/blockifier/src/execution/syscalls/syscalls_test.rs
…-engine # Conflicts: # Cargo.lock
…cution-engine # Conflicts: # Cargo.lock
…cution-engine # Conflicts: # Cargo.lock # crates/blockifier/src/execution/contract_class.rs
varex83
changed the title
NativeSyscallHandlerNativeSyscallHandler
There was a problem hiding this comment.
Reviewed 18 of 22 files at r1, all commit messages.
Reviewable status: 18 of 22 files reviewed, all discussions resolved
There was a problem hiding this comment.
Reviewed 1 of 22 files at r1.
Reviewable status: 19 of 22 files reviewed, all discussions resolved
There was a problem hiding this comment.
Reviewed 1 of 22 files at r1.
Reviewable status: 20 of 22 files reviewed, 1 unresolved discussion (waiting on @varex83)
crates/blockifier/src/execution/native/utils_test.rs line 29 at r1 (raw file):
let res = decode_felts_as_str(&felts); dbg!(res.as_bytes());
Is the print here intentional? If so, what is its purpose?
Code quote:
dbg!(res.as_bytes());There was a problem hiding this comment.
Reviewed 1 of 22 files at r1.
Reviewable status: 21 of 22 files reviewed, 1 unresolved discussion (waiting on @varex83)
…call-handler # Conflicts: # crates/blockifier/src/execution/native/utils.rs
There was a problem hiding this comment.
Reviewable status: 16 of 22 files reviewed, 1 unresolved discussion (waiting on @meship-starkware)
crates/blockifier/src/execution/native/utils_test.rs line 29 at r1 (raw file):
Previously, meship-starkware (Meshi Peled) wrote…
Is the print here intentional? If so, what is its purpose?
Done.
There was a problem hiding this comment.
Reviewed 2 of 3 files at r3, 2 of 4 files at r4, all commit messages.
Reviewable status: 20 of 22 files reviewed, all discussions resolved
rodrigo-pino
added
the
native integration
|
Solved in #1240 |
This PR is follow-up after #429
This change is