This repository was archived by the owner on Oct 31, 2023. It is now read-only.
Change verify function visibility from external to public to enable inheritance#176
Closed
Turupawn wants to merge 1 commit intonoir-lang:masterfrom
Closed
Change verify function visibility from external to public to enable inheritance#176Turupawn wants to merge 1 commit intonoir-lang:masterfrom
Turupawn wants to merge 1 commit intonoir-lang:masterfrom
Conversation
Member
|
Hi @Turupawn, the verifier contracts aren't actually developed/tested in this repository but in https://github.com/AztecProtocol/aztec-verifier-contracts and so we'd like to ensure that we don't introduce any changes relative to that repository. For that reason I'm going to close this PR as it stands. However please feel free to open an issue/PR on that repository to discuss with the team which develops the verifier smart contracts. We'll then update to pull down any changes they make. |
Member
|
Sorry for any time wasted by this, I'll make a note in the readme about the repository for the verifier contracts. |
Author
|
Thanks @TomAFrench , moved it there: |
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The problem
It should be common for devs to inherit from
UltraVerifierwhile creating a dApp. This is to keep the codebase organized and readable. A normal implementation should look like the following example:However this is currently not possible due to the
verifyfunction beingexternal. This means that this function is not visible to inherited contracts.The solution
I think the
verifyvisibility should be changed topublic. This will enableverifybeing called from inherited contracts like the example above.