Start developing property testing #8
Conversation
virgil-serbanuta
force-pushed
the
foundry-like
branch
2 times, most recently
from
82affcc
to
ffbdcd6
Compare
virgil-serbanuta
force-pushed
the
foundry-like
branch
from
dc3a14a
to
e92dbfe
Compare
| assert len(list(kcfg.successors(node.id))) == 0 | ||
|
|
||
| logs: dict[int, tuple[LogEntry, ...]] = {} | ||
| max_depth = 1 |
There was a problem hiding this comment.
Why one step at a time? Doesn't it cause an rpc call overhead?
There was a problem hiding this comment.
Yes, it does, I think that the overhead more than 1 second / RPC call. I can change it if you think I should do it in this PR.
However, the intent of this PR was to create a basic framework for execution. It is supposed to be relatively small, in order to make it easy to review. At the same time, it is heavily biased towards debugging, since execution does not get that far anyway.
The version on which I'm working right now has a much larger depth, and it manages to finish the proof you sent me. I'm not sure how I'll split it into PRs, though, so I can't promise that max_depth will be updated in the next one.
Co-authored-by: Burak Bilge Yalçınkaya <[email protected]>
* Start developing property testing * Update the Elrond semantics * Update kmxwasm/src/kmxwasm/proofs.py Co-authored-by: Burak Bilge Yalçınkaya <[email protected]> --------- Co-authored-by: Burak Bilge Yalçınkaya <[email protected]>
No description provided.