8000 [6.2] IRGen: Emit objc type encoding for ivars by kastiglione · Pull Request #82591 · swiftlang/swift · GitHub
[go: up one dir, main page]

Skip to content

[6.2] IRGen: Emit objc type encoding for ivars #82591

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

Merged

Conversation

kastiglione
Copy link
Contributor
@kastiglione kastiglione commented Jun 27, 2025

ObjC ivar metadata has up to now emitted an empty string for the ivar's objc type encoding. Conversely, ObjC property metadata is emitted with an objc type encoding. This changes the compiler to also emit an objc type encoding for ivars.

The motivation for this change is for lldb to print ivars of classes declared in Objective-C but implemented in Swift, as defined in [SE-0436](https://github.com/swiftlang/swift-evolution/blob/main/proposals/0436-objc-implementation.md). Without the presence of type encoding for ivars, lldb is unable to present to the user the ivars/properties of instances of such classes.

rdar://138569299
(cherry picked from commit ce7a3b3)
@kastiglione kastiglione changed the title IRGen: Emit objc type encoding for ivars [6.2] IRGen: Emit objc type encoding for ivars Jun 27, 2025
@kastiglione kastiglione marked this pull request as ready for review June 27, 2025 23:25
@kastiglione kastiglione requested a review from a team as a code owner June 27, 2025 23:25
@kastiglione
Copy link
Contributor Author

@swift-ci test

@adrian-prantl adrian-prantl merged commit 9b67659 into release/6.2 Jun 30, 2025
5 checks passed
@adrian-prantl adrian-prantl deleted the dl/IRGen-Emit-objc-type-encoding-for-ivars branch June 30, 2025 19:50
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
0