fix(noirc_errors): Switch update_acir to use for-loop instead of iter#2646
Closed
fix(noirc_errors): Switch update_acir to use for-loop instead of iter#2646
Conversation
Member
|
I've got an existing PR for this here: #2643 |
Contributor
Author
|
@TomAFrench oops I missed that thanks! |
This file contains hidden or 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
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.
Description
Problem*
Some context here: #2645 (comment)
Iterators are lazy in Rust. In
update_acirwe did not use the iterator for new_locations. This means we are callingmem::takeon our location data, but never inserting back into it, thus removing all our runtime location data.Summary*
Documentation
This PR requires documentation updates when merged.
Additional Context
PR Checklist*
cargo fmton default settings.