Repository navigation
do not relabel delegation edge after writing to underlying value - #191
Merged
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
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.
The PCG would relabel delegation edges after writing to the underlying value. Therefore, writing to the underlying value (e.g., through a mutef) would decouple the mutref from a derived raw pointer. Afterwards, the PCG might convert the mutef to a generic type even though we are still accessing the rawptr. The following snippet shows this issue:
This PR fixes this issue by preventing delegation edges from being relabelled after writing to a place.
Disclaimer: This PR was written using Claude Code.