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

[SR-4343] Decide what class metadata is opaque for library evolution (resilience) #46922

Closed
bob-wilson opened this issue Mar 24, 2017 · 2 comments
Labels
affects ABI Flag: Affects ABI compiler The Swift compiler itself task

Comments

@bob-wilson
Copy link
Contributor

Previous ID SR-4343
Radar rdar://problem/31408029
Original Reporter @bob-wilson
Type Task
Status Resolved
Resolution Done

Attachment: Download

Additional Detail from JIRA
Votes 0
Component/s Compiler
Labels Task, AffectsABI
Assignee @duyduongdevelopers (JIRA)
Priority Medium

md5: 1e052641a819da11506e71ae7ed0906d

Issue Description:

From the Class Metadata section of the ABI Stability manifesto:

"Library evolution may present many changes to what exactly is present and will likely make many of the contents opaque to accommodate changes."

We need to decide what the class metadata should contain and what should be opaque as part of locking down the ABI.

@bob-wilson
Copy link
Contributor Author

@swift-ci create

@slavapestov
Copy link
Contributor

I think this is done. We've essentially made everything opaque except for the generic parameter area.

@swift-ci swift-ci transferred this issue from apple/swift-issues Apr 25, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects ABI Flag: Affects ABI compiler The Swift compiler itself task
Projects
None yet
Development

No branches or pull requests

2 participants