Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(interpreter): OpCode struct constants #1173

Merged
merged 1 commit into from
Mar 8, 2024

Conversation

DaniPopes
Copy link
Collaborator

Currently the only way to instantiate an OpCode at compile time is by using unsafe or matching on the Option returned by new (unwrap is not stable). This PR adds the same u8 opcode constants to the OpCode struct as well.

Currently the only way to instantiate an OpCode at compile time is by using
unsafe or matching on the Option returned by `new` (unwrap is not stable).
This PR adds the same `u8` opcode constants to the `OpCode` struct as well.
@rakita rakita merged commit 2f96098 into bluealloy:main Mar 8, 2024
25 checks passed
@DaniPopes DaniPopes deleted the opcode-constants branch March 8, 2024 22:41
@github-actions github-actions bot mentioned this pull request Mar 8, 2024
fubuloubu pushed a commit to ApeWorX/revm that referenced this pull request Apr 11, 2024
Currently the only way to instantiate an OpCode at compile time is by using
unsafe or matching on the Option returned by `new` (unwrap is not stable).
This PR adds the same `u8` opcode constants to the `OpCode` struct as well.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants