neoneo-go/pkg/vm/opcode/opcode_test.go

package opcode

import (
	"testing"

	"github.com/stretchr/testify/assert"
)

// Nothing more to test here, really.
func TestStringer(t *testing.T) {
	tests := map[Opcode]string{
		ADD:    "ADD",
		SUB:    "SUB",
		ASSERT: "ASSERT",
		0xff:   "Opcode(255)",
	}
	for o, s := range tests {
		assert.Equal(t, s, o.String())
	}
}
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 14:05:06 +00:00			`package opcode`

			`import (`
			`"testing"`

			`"github.com/stretchr/testify/assert"`
			`)`

			`// Nothing more to test here, really.`
			`func TestStringer(t *testing.T) {`
			`tests := map[Opcode]string{`
vm: implement ASSERT/ABORT opcodes Rename THROWIFNOT to ASSERT, add ABORT opcode. ABORT cannot be caught, but the implementation should be postponed until exception handling is implemented. 2020-05-06 12:54:18 +00:00			`ADD: "ADD",`
			`SUB: "SUB",`
			`ASSERT: "ASSERT",`
			`0xff: "Opcode(255)",`
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 14:05:06 +00:00			`}`
			`for o, s := range tests {`
			`assert.Equal(t, s, o.String())`
			`}`
			`}`