-
Notifications
You must be signed in to change notification settings - Fork 248
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
chore(nargo): abstract paths from nargo's working directory #761
Merged
Conversation
This file contains 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
jfecher
reviewed
Feb 8, 2023
jfecher
approved these changes
Feb 10, 2023
TomAFrench
added a commit
that referenced
this pull request
Feb 14, 2023
* master: (28 commits) chore(ci): Add release token to enable runs against release PR (#840) feat(ssa): array sort (#754) chore: update readme (#811) chore: fix clippy (#825) chore: remove stale comment on HirFunction.unchecked_from_expr (#827) chore: Getter naming refactor (#803) chore: updated "HirFunction::unsafe_from_expr" to "HirFunction::unchecked_from_expr" (#823) chore: Forbid unsafe code (#824) chore: Follow rust naming convention (#801) feat(ci): Add concurrency group for rust workflow (#806) chore(ssa): rename impl method to follow Rust guideline (#782) fix(nargo): `nargo test` now only runs test functions defined in the current module (#805) chore(nargo): Remove outdated error message when Prover/Verifier.toml is missing (#807) chore(ssa): rename codegen to ssa_gen + reorg of `Value` struct (#797) chore(nargo): abstract paths from nargo's working directory (#761) chore(ci): Rename workflows (#804) feat: Impls with generics (#798) chore(ssa): Add doc comments on `Opcode` struct (#778) fix: operators issuing type errors when used with matching integer types arising from generic code (#789) chore(nargo)!: bump MSRV to 1.66.0 (#799) ...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Related issue(s)
Description
Summary of changes
Currently we make assumptions in a number of places that
nargo
is running in the project directory which we want to interact with. This isn't ideal in a CI or workspace contexts as often the noir project of interest will be in a deeper directory compared to wherenargo
is run.I've made the directory relative to which
nargo
should perform its actions (saving circuits, reading inputs, etc.) explicit with thepaths
option. After testing this I have then removed the flag from the CLI so people don't start relying on this (We don't really want people to pass in paths directly rather than having some form of workspace).Dependency additions / changes
N/A
Test additions / changes
N/A
Checklist
cargo fmt
with default settings.Additional context