-
Notifications
You must be signed in to change notification settings - Fork 3
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
Added support for named list arguments #1151
Merged
EagleoutIce
merged 32 commits into
main
from
1139-add-support-for-named-list-arguments-field-sensitive-pointer-analysis
Jan 5, 2025
Merged
Added support for named list arguments #1151
EagleoutIce
merged 32 commits into
main
from
1139-add-support-for-named-list-arguments-field-sensitive-pointer-analysis
Jan 5, 2025
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
8a2d646
to
3e1384d
Compare
f5c30b5
to
8417576
Compare
3bc497c
to
25d8b0d
Compare
0216e11
to
c578925
Compare
This way only the correct definition is stored. Any overwritten definition isn't stored anymore. Currently, this only works for definition that happen in each branch.
The merge indices logic was merged to a separate method. When there are indices defined, then the function is not marked as maybe. This enables overwriting the previous indices.
Before, an access to a list object would reference the whole object, now that's only when the list function is called. Single assignments are referenced directly by their access operator. This allows us to skip not relevant list accesses.
To ensure a executable slice, the list call has to be always in the slice.
When a list is redefined the former definiton is replaced, therefore storing the indices would cause keeping the previous definition in the slice.
Nested list access comes with new complications. For each list in the root index, the names must be resolved recursively, to reference the correct index.
This enables nested defintion/access/assignment.
This is done recursively to include all indices that had an impact on the result.
c578925
to
71f7d2b
Compare
Also inverted semantic
This way, they can be accessed by the write and read operations
This pull request is included in v2.1.10 (see Release v2.1.10 (First support for pointer analysis (named list arguments with |
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.
Closes #1139
Added