-
Notifications
You must be signed in to change notification settings - Fork 219
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
Add --expression_width
flag to nargo compile
#3854
Comments
|
Yep, I'll rename |
kevaundray
changed the title
Add
Add Dec 19, 2023
--program_width
flag to nargo compile--expression_width
flag to nargo compile
kevaundray
changed the title
Add
Add Jan 15, 2024
--expression_width
flag to nargo compile--expression-width
flag to nargo compile
kevaundray
changed the title
Add
Add Jan 15, 2024
--expression-width
flag to nargo compile--expression_width
flag to nargo compile
5 tasks
github-merge-queue bot
pushed a commit
that referenced
this issue
Jan 25, 2024
# Description ## Problem\* Resolves #3854 ## Summary\* This PR adds the `expression-width` option to the CLI which allows users to specify the expression width they want to use. Passing zero will result in an unbounded width. ## Additional Context ## Documentation\* Check one: - [ ] No documentation needed. - [ ] Documentation included in this PR. - [ ] **[Exceptional Case]** Documentation to be submitted in a separate PR. # PR Checklist\* - [ ] I have tested the changes locally. - [ ] I have formatted the changes with [Prettier](https://prettier.io/) and/or `cargo fmt` on default settings. --------- Co-authored-by: kevaundray <kevtheappdev@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem
This adds the ability to tell the compiler which expression width to use instead of getting it from the default backend
Happy Case
.
Alternatives Considered
No response
Additional Context
No response
Would you like to submit a PR for this Issue?
No
Support Needs
No response
The text was updated successfully, but these errors were encountered: