Skip to content
This repository was archived by the owner on Apr 9, 2024. It is now read-only.

Split off errors from OpcodeResolution#39

Merged
kevaundray merged 3 commits intonoir-lang:masterfrom
TomAFrench:opcode-resolution-error
Dec 27, 2022
Merged

Split off errors from OpcodeResolution#39
kevaundray merged 3 commits intonoir-lang:masterfrom
TomAFrench:opcode-resolution-error

Conversation

@TomAFrench
Copy link
Copy Markdown
Member

This implements the changes described in noir-lang/noir#520 (comment).

This is sensible imo as

  • OpcodeResolution doesn't make sense for a circuit-level function such as PartialWitnessGenerator.solve (what does "Skip" mean when solving a circuit?)
  • We can define error messages here in ACVM for the failure modes of solving the circuit. Callers then don't need to understand the reasoning behind all the OpcodeResolution variants to be able to separate success vs failure.

I've lumped in a change to simplify BlackBoxFuncCall in the last commit which improves readability imo, happy to revert this if this is unwanted.

@kevaundray
Copy link
Copy Markdown
Contributor

haha was thinking of doing something similar! This looks good to me overall, I've opened an issue re UnknownError, but its not a blocker for this, so happy to merge

@kevaundray kevaundray merged commit 86d6168 into noir-lang:master Dec 27, 2022
@TomAFrench TomAFrench deleted the opcode-resolution-error branch December 28, 2022 00:23
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants