ecall: avoid internal name collision in abstract_pvs#1038
Merged
Conversation
Thread hyps through the per-memory fold so each pass reserves its freshly minted `<symbol>_' names before the next memory is processed. Previously both sides freshened against the original hyps, so a contract argument naming the same program variable on both sides produced two identically-named idents, and t_intros_i rejected the second.
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
1 participant
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.
Thread hyps through the per-memory fold so each pass reserves its
freshly minted `_' names before the next memory is processed.
Previously both sides freshened against the original hyps, so a contract
argument naming the same program variable on both sides produced two
identically-named idents, and t_intros_i rejected the second.
Closes #1037