Improve Rename in clone, and fix uniqueness laws
#296
Merged
Conversation
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
dorchard
changed the title
Rename in cloneRename in clone, and fix uniqueness laws
takanuva
approved these changes
Dec 18, 2025
dorchard
force-pushed
the
fix-uniquness-example
branch
from
4cdd1b1 to
5283062
Compare
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.
This fixes issue #295 also this fixes the failing test in
example/uniqueness.gr. It does the followingRenametype level function to now haveRename oldId newId adefined as hunting for all free occurences ofoldIdinside ofaand replacing them withnewId. This is closer to the paper.