-
Notifications
You must be signed in to change notification settings - Fork 229
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: introduce codegen-verifier section to Nargo.toml #1138
Conversation
nargo codegen-verifier
nargo codegen-verifier
Hi, Thank you for contributing to the Noir repository :) The issue which you are aiming to solve has additional context here given by @TomAFrench here. Its a bit more than just a folder rename! |
Thanks for letting me know! I misread that the configurable folder name might be a different PR. 😅 I'll be back after implementation. |
nargo codegen-verifier
@kevaundray @TomAFrench PTAL 😄 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your help with this issue @longfin
The PR's looking pretty good, I've made a couple of small notes.
c5ecd2d
to
31577ac
Compare
@TomAFrench Thanks a lot for the detailed review! I guess that most of them are addressed on 31577ac. Please take a look and feel free to let me know about remaining or other comments. 😄 |
I'll be back after fixing it 😓 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @longfin, it's looking really good now. I'm going to merge this soon but I need to add an issue for the feature I mentioned so we can link to that.
/// TODO: Move this function to `PackageManifest` after tracking the root directory. | ||
/// See also: https://github.com/noir-lang/noir/pull/1138#discussion_r1165351237 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll make a quick issue detailing this and then we can update this to point at that issue.
@TomAFrench barring conflicts, can we merge this? |
I'll take a look today. 💪 |
@kevaundray @TomAFrench In general cases, I prefer to rebase instead of merging since I don't want to leave a merge commit unnecessarily. but my branch already has been exposed and is containing @TomAFrench's commits. In this case, is there any existing way that the team prefers between merge or rebase? |
Hey, sorry for the delay on this PR. @longfin A merge commit into this branch is fine as we'll be squashing all the commits when we merge into master. Rebasing causes some issues when it comes to reviewing (we need to check the entire PR again rather than just the new commit) so we try not to do them once others have started looking at the PR. |
Conflicts resolved. @TomAFrench is there a new issue for this comment? |
Oops, some tests seem to fail. I'll check again. |
This PR removes the `nargo codegen-verifier` command and replaces it with an example bash script showing how to use `nargo` in conjunction with `bb` to generate a smart contract verifier. cc @AztecProtocol/devrel Closes noir-lang/noir#4447 Closes noir-lang/noir#1138 Closes noir-lang/noir#2222 Closes noir-lang/noir#1159 Closes noir-lang/noir#1009 Closes noir-lang/noir#3837 Closes noir-lang/noir#2667 --------- Co-authored-by: ludamad <[email protected]> Co-authored-by: Maxim Vezenov <[email protected]>
Related issue(s)
Resolves #1009
Description
Summary of changes
Added
codegen-verifier
section toNargo.toml
, to enable to config the output directory fornargo codegen-verifier
command.Dependency additions / changes
N/A (maybe 😅 )
Test additions / changes
Checklist
cargo fmt
with default settings.Documentation needs
Additional context