Skip to content
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

SILGen: Coordinate access strategy determination with actual codegen in findStorageReferenceExprForMoveOnly. #78572

Merged

Conversation

jckarter
Copy link
Contributor

Looking at the AST-level getReadImpl doesn't always correspond to what accessor SILGen prefers to use, due to resilience, ABI rules, and other concerns. In findStorageReferenceExprForMoveOnly, when determining whether a storage reference is borrowable, use the same logic as SILGenLValue actually uses to determine what storage or accessor access strategy to use.

Fixes rdar://142509673

…in `findStorageReferenceExprForMoveOnly`.

Looking at the AST-level `getReadImpl` doesn't always correspond to what
accessor SILGen prefers to use, due to resilience, ABI rules, and other
concerns. In findStorageReferenceExprForMoveOnly, when determining whether
a storage reference is borrowable, use the same logic as SILGenLValue actually
uses to determine what storage or accessor access strategy to use.

Fixes rdar://142509673
@jckarter jckarter requested a review from kavon as a code owner January 11, 2025 01:26
@jckarter
Copy link
Contributor Author

@swift-ci Please test

@jckarter jckarter merged commit 01faf1f into swiftlang:main Jan 13, 2025
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant