Pexe inspect plan fixes - #228
Open
robknight wants to merge 4 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #222
Fixes
pexe inspectso that instead of using the low-level Podlang predicates, it uses the high-level Rhai AST to infer information about object/action structure. This is used for:pexe inspect plan- explains how a real transaction proof for a given action would be built, e.g. which statements it uses and how many PODspexe inspect prove- generates a real proof from mock datapexe inspect classes- lists classes and their fields and constraints (where possible to infer)This previously worked for the limited examples we had, but worked much less well for the larger
microverseexample, with panics and excessive memory usage. Switching to the more reliable source of information about the actions/classes solves the issue.