This repository has been archived by the owner on Apr 9, 2024. It is now read-only.
feat(acvm)!: Remove OpcodeResolution
enum
#400
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.
Description
Problem*
Summary*
The assumption made in #399 that each opcode will be immediately executable means that we no longer need to track multiple different potential outcomes of an opcode - it either succeeds or fails. There's a slight special case with Brillig where it may require a foreign call but that's easy to handle.
Additional Context
PR Checklist*
cargo fmt
on default settings.