neoneo-go/pkg
Roman Khimov 8d4dd2d2e1 vm: move opcodes into their own package
This allows easier reuse of opcodes and in some cases allows to eliminate
dependencies on the whole vm package, like in compiler that only needs opcodes
and doesn't care about VM for any other purpose.

And yes, they're opcodes because an instruction is a whole thing with
operands, that's what context.Next() returns.
2019-12-03 18:22:14 +03:00
..
consensus vm: move opcodes into their own package 2019-12-03 18:22:14 +03:00
core vm: move opcodes into their own package 2019-12-03 18:22:14 +03:00
crypto Merge pull request #467 from nspcc-dev/errcheck_297 2019-12-03 15:06:11 +03:00
internal/keytestcases crypto: add invalid testcase 2019-11-29 11:03:03 +03:00
interop fix spelling and godoc comments 2019-10-22 17:56:03 +03:00
io io: refactoring for using WriteVarBytes instead of WriteLE 2019-12-03 13:49:33 +03:00
network Merge pull request #467 from nspcc-dev/errcheck_297 2019-12-03 15:06:11 +03:00
rpc vm: move opcodes into their own package 2019-12-03 18:22:14 +03:00
smartcontract vm: move opcodes into their own package 2019-12-03 18:22:14 +03:00
util util: add missing tests for Uint256 2019-11-25 11:55:26 +03:00
vm vm: move opcodes into their own package 2019-12-03 18:22:14 +03:00
wallet crypto: add invalid testcase 2019-11-29 11:03:03 +03:00