Skip to content

SILGen: Handle struct fields and addressors as addressable storage. #82288

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

Conversation

jckarter
Copy link
Contributor

When accessing stored properties out of an addressable variable or parameter binding, the stored property's address inside the addressable storage of the aggregate is itself addressable. Also, if a computed property is implemented using an addressor, treat that as a sign that the returned address should be used as addressable storage as well. rdar://152280207

When accessing stored properties out of an addressable variable or parameter
binding, the stored property's address inside the addressable storage of the
aggregate is itself addressable. Also, if a computed property is implemented
using an addressor, treat that as a sign that the returned address should be
used as addressable storage as well. rdar://152280207
@jckarter jckarter requested a review from atrick June 17, 2025 03:27
@jckarter jckarter requested a review from eeckstein as a code owner June 17, 2025 03:27
@jckarter
Copy link
Contributor Author

@swift-ci Please test

@atrick
Copy link
Contributor

atrick commented Jun 17, 2025

Fantastic! There are only two FIXMEs left in my @_addressable tests now
2871aa2
I'll make sure there are separate radars for those.

@jckarter jckarter merged commit b8f5a36 into swiftlang:main Jun 17, 2025
5 checks passed
Copy link
Contributor

@atrick atrick left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fantastic! Thank you. Looks good for 6.2.

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.

2 participants