core/vm: don't use iota for opcode definitions #23928
Merged
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.
This cleans up a pet peeve I've had for years.
iota
is useful when we don't really care what number something winds up with, we just want an enum-like thing which has a certain ordering between elements.Opcodes, however, are externally defined. It's IMO wrong to assign them by using
iota
, as if we don't really care what numberCALL
maps to internally.Aside from that, having it directly defined as in this PR makes it easier to check a particular opcode-to-byte with eyes alone, without relying on IDE magic to infer the actual number for you.