-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rust ref pattern #18754
Open
paldepind
wants to merge
5
commits into
github:main
Choose a base branch
from
paldepind:rust-ref-pattern
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Rust ref pattern #18754
Conversation
This file contains 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
341c62f
to
be6ac13
Compare
paldepind
commented
Feb 12, 2025
any(SelfParam sp | | ||
definingNode = sp.getName() and | ||
name = sp.getName().getText() and | ||
private predicate variableDecl(AstNode definingNode, Name name, string text) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is an orthogonal refactor, but since I was making changes around Name
it occurred to me that it might be nice to have Name
here, since both SelfParam
and IdentPat
have that in common.
To do this we: * Let SSA writes target the name inside identifier patterns instead of the pattern itself * Include relevant names in the data flow graph * Add a store step from a identifier patterns with `ref` into the contained name. So we have an edge `ref a` -> `a` that stores in the reference content type.
be6ac13
to
7476aea
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 PR aims to add support for
ref
in patterns.For a
let
statement these two lines are equivalent:So we'd like their effect to be the same. For a pattern like
Some(ref a)
the introduced variablea
is a reference and should have the content of the matched value stored in the reference content type.The cleanest way to do this is to add a new store edge from
ref a
(identity pattern) ->a
(name) in the data flow graph. But, currently the name nodes in the AST are not really considered everywhere from the CFG to the data flow library.Hence this PR:
ref
into the contained name. So we have an edgeref a
->a
that stores in the reference content type. For identifier patterns without aref
we add a normal value preserving step, that maintains current behavior.Here are some diagrams depicting the change in the CFG.
Example 1
Here there is a new
map
node before themut map
node.Before
After
Example 2
This shows that the PR also makes a change regarding splitting, in that it is no longer done for identifier patterns.
Before
After