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
Compile the program above wit nargo v0.23.0 or 0.24.0
Project Impact
Blocker
Impact Context
I've had an issue in my tests that the assertion were firing in the wrong order. I saw that it's fixed in 0.24. Tried to upgrade to 0.24, but encountered a compilation panic. Tried to find the minimal example and found the one here which funnily is also happening on 0.23.
Therefore without this fixed I would be stuck on 0.23 and will need to have wrong assertion messages in test expects
Workaround
None
Workaround Description
No response
Additional Context
No response
Installation Method
Binary (noirup default)
Nargo Version
No response
NoirJS Version
No response
Would you like to submit a PR for this Issue?
None
Support Needs
No response
The text was updated successfully, but these errors were encountered:
# Description
## Problem\*
Resolves#4407
## Summary\*
We currently have no way to gracefully error during monomorphization and
so must panic if we run into any errors.
This PR then adds the `MonomorphizationError` enum with an example error
type. We've also added a `CompileError` which unifies `RuntimeError` and
`MonomorphizationError` so they can be converted into `FileDiagnostic`s
## Additional Context
## Documentation\*
Check one:
- [x] No documentation needed.
- [ ] Documentation included in this PR.
- [ ] **[Exceptional Case]** Documentation to be submitted in a separate
PR.
# PR Checklist\*
- [x] I have tested the changes locally.
- [x] I have formatted the changes with [Prettier](https://prettier.io/)
and/or `cargo fmt` on default settings.
Aim
I've tried to compile this code. I understand that it's incorrect, but it should not cause compiler panic.
Expected Behavior
I get the compilation error
Bug
I get compiler panic
To Reproduce
Project Impact
Blocker
Impact Context
I've had an issue in my tests that the assertion were firing in the wrong order. I saw that it's fixed in 0.24. Tried to upgrade to 0.24, but encountered a compilation panic. Tried to find the minimal example and found the one here which funnily is also happening on 0.23.
Therefore without this fixed I would be stuck on 0.23 and will need to have wrong assertion messages in test expects
Workaround
None
Workaround Description
No response
Additional Context
No response
Installation Method
Binary (
noirup
default)Nargo Version
No response
NoirJS Version
No response
Would you like to submit a PR for this Issue?
None
Support Needs
No response
The text was updated successfully, but these errors were encountered: