diff options
author | John Jannotti <john.jannotti@algorand.com> | 2022-01-10 13:30:11 -0500 |
---|---|---|
committer | GitHub <noreply@github.com> | 2022-01-10 13:30:11 -0500 |
commit | b70783e36e32239ccaad32f4b94e1085d4b1bbfe (patch) | |
tree | ce0daa7d80193ee6460113776e6fdc8c9efc9727 | |
parent | d2594fb1ab0cc6d0a36c7202beaf5c321e074781 (diff) |
Feature/contract to contract (#3401)
* Three new globals for to help contract-to-contract usability
* detritis
* Check error
* doc comments
* Impose limits on the entire "tree" of inner calls.
This also increases the realism of testing of multiple app calls in a
group by creating the EvalParams with the real constructor, thus
getting the pooling stuff tested here without playing games
manipulating the ep after construction.
* Move appID tracking into EvalContext, out of LedgerForLogic
This change increases the seperation between AVM execution and the
ledger being used to lookup resources. Previously, the ledger kept
track of the appID being executed, to offer a narrower interface to
those resources. But now, with app-to-app calls, the appID being
executed must change, and the AVM needs to maintain the current appID.
* Stupid linter
* Fix unit tests error messages
* Allow access to resources created in the same transaction group
The method will be reworked, but the tests are correct and want to get
them visible to team.
* Access to apps created in group
Also adds some tests that are currently skipped for testing
- access to addresses of newly created apps
- use of gaid in inner transactions
Both require some work to implement the thing being tested.
* Remove tracked created mechanism in favor of examining applydata.
* Allow v6 AVM code to use in-group created asas, apps (& their accts)
One exception - apps can not mutate (put or del) keys from the app
accounts, because EvalDelta cannot encode such changes.
* lint docs
* typo
* The review dog needs obedience training.
* Use one EvalParams for logic evals, another for apps in dry run
We used to use one ep per transaction, shared between sig and and
app. But the new model of ep usage is to keep using one while
evaluating an entire group.
The app ep is now built logic.NewAppEvalParams which, hopefully, will
prevent some bugs when we change something in the EvalParams and don't
reflect it in what was a "raw" EvalParams construction in debugger and
dry run.
* Use logic.NewAppEvalParams to decrease copying and bugs in debugger
* Simplify use of NewEvalParams. No more nil return when no apps.
This way, NewEvalParams can be used for all creations of EvalParams,
whether they are intended for logicsig or app use, greatly simplifying
the way we make them for use by dry run or debugger (where they serve
double duty).
* Remove explicit PastSideEffects handling in tealdbg
* Always create EvalParams to evaluate a transaction group.
We used to have an optimization to avoid creating EvalParams unless
there was an app call in the transaction group. But the interface to
allow transaction processing to communicate changes into the
EvalParams is complicated by that (we must only do it if there is
one!)
This also allows us to use the same construction function for eps
created for app and logic evaluation, simplifying dry-run and
debugger.
The optimization is less needed now anyway:
1) The ep is now shared for the whole group, so it's only one.
2) The ep is smaller now, as we only store nil pointers instead of
larger scratch space objects for non-app calls.
* Correct mistaken commit
* Spec improvments
* More spec improvments, including resource "availability"
* Recursively return inner transaction tree
* Lint
* No need for ConfirmedRound, so don't deref a nil pointer!
* license check
* Shut up, dawg.
* base64 merge cleanup
0 files changed, 0 insertions, 0 deletions