chore: create unknown opcodes as unchecked #88
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
DaniPopes
reviewed
Apr 7, 2024
| OpCode::new(invalid_opcode) | ||
| }) | ||
| .expect("is valid opcode;"); | ||
| let op = OpCode::new(value).unwrap_or_else(|| { |
There was a problem hiding this comment.
Why unwrap_or_else? Also cc bluealloy/revm#1215
This is what I meant when removing unsafe from new_unchecked.
There was a problem hiding this comment.
good point, we can just do new_unched here
mattsse
added a commit
that referenced
this pull request
Apr 7, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 could be an opcode that is manually added to the evm