-
Notifications
You must be signed in to change notification settings - Fork 224
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: add compile-time assertions on generic arguments of stdlib functions #6981
base: master
Are you sure you want to change the base?
Conversation
…tatic_assert locations for field/mod.nr
Compilation Report
|
Execution Report
|
Compilation Memory Report
|
Execution Memory Report
|
…cks for numeric generics in field/mod.nr, fixed printing in test_transform_program_is_idempotent
…c_assert, ensure dynamic vars rejected by static_assert
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.
We shouldn't split into safe and unsafe variants but instead have a check that the decomposition is canonical similar to how we do it for byte decompositions.
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.
- How would
a check that the decomposition is canonical
work at compile-time? I would expect to check that it's canonical in Add feature-gated runtime assertions to stdlib functions #6964 - R.e. avoiding splitting into safe and unsafe versions, do you mean to move these checks into the
builtin
function implementations?
Changes to Brillig bytecode sizes
🧾 Summary (10% most significant diffs)
Full diff report 👇
|
Description
Problem*
Resolves #6962
Summary*
Additional Context
Documentation*
Check one:
PR Checklist*
cargo fmt
on default settings.