chore: SliceRemove minor optimization#3652
Conversation
… heavy cleanup still needed
…y modify the predicate index for the non-dummy val
…et element type size array correct
Co-authored-by: Tom French <15848336+TomAFrench@users.noreply.github.com>
Co-authored-by: Tom French <15848336+TomAFrench@users.noreply.github.com>
Co-authored-by: Tom French <15848336+TomAFrench@users.noreply.github.com>
Co-authored-by: Tom French <15848336+TomAFrench@users.noreply.github.com>
# Description ## Problem\* Resolves #2462 ## Summary\* This PR simply builds upon #3617 by including some tests that use a dynamic index on SliceInsert and SliceRemove. ## 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\* - [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.
Changes to circuit sizes
🧾 Summary (10% most significant diffs)
Full diff report 👇
|
|
Can we remove this write operation entirely? We've already initialised the array so if we don't care about the value written here we can just leave it as is, right? |
I switched to initializing without the original slice value to avoid having to clone the |
|
@TomAFrench It looks to have reduced the ACIR opcodes for |
Description
Problem*
Resolves this discussion #3617 (comment)
Summary*
Reference the discussion and the PR it is under for more context.
Additional Context
Documentation*
Check one:
PR Checklist*
cargo fmton default settings.