mirror of
https://github.com/nspcc-dev/neo-go.git
synced 2024-11-27 03:58:06 +00:00
fe1f0a7245
At the moment we should have 3 possible options to check return state during vm context unloading: * no check * ensure the stack is empty * ensure the stack is not empty It is necessary to distinguish them because new _deploy method shouldn't left anything on stack. Example: if we use _deploy method before some ordinary contract method which returns one value. Without these changes the contract invocation will fail due to 2 elements on stack left after invocation (the first `null` element is from _deploy, the second element is return-value from the ordinary contract method). |
||
|---|---|---|
| .. | ||
| cli | ||
| emit | ||
| opcode | ||
| stackitem | ||
| testdata | ||
| context.go | ||
| contract_checks.go | ||
| contract_checks_test.go | ||
| debug_test.go | ||
| exception.go | ||
| interop.go | ||
| interop_iterators.go | ||
| json_test.go | ||
| ref_counter.go | ||
| ref_counter_test.go | ||
| slot.go | ||
| slot_test.go | ||
| stack.go | ||
| stack_test.go | ||
| state.go | ||
| state_test.go | ||
| vm.go | ||
| vm_test.go | ||