You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 18, 2023. It is now read-only.
Hello, I'm writing educational content about Noir in spanish and @critesjosh has been guiding me on the process. I stumbled into following issue while writing a guide on how to create a dApp. I got redirected here from acvm-backend-barretenberg.
I did a PR #23 that solves this. Happy to hear your comments.
The problem
It should be common for devs to inherit from UltraVerifier while creating a dApp. This is to keep the codebase organized and readable. A normal implementation should look like the following example:
Hello, I'm writing educational content about Noir in spanish and @critesjosh has been guiding me on the process. I stumbled into following issue while writing a guide on how to create a dApp. I got redirected here from acvm-backend-barretenberg.
I did a PR #23 that solves this. Happy to hear your comments.
The problem
It should be common for devs to inherit from
UltraVerifier
while 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
verify
function beingexternal
. This means that this function is not visible to inherited contracts.The solution
I think the
verify
visibility should be changed topublic
. This will enableverify
being called from inherited contracts like the example above.The text was updated successfully, but these errors were encountered: