[SR-4352] Runtime changes for library evolution and ownership

[bob-wilson]

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

Additional Detail from JIRA

Votes	0
Component/s	Compiler
Labels	Task, AffectsABI
Assignee	@bob-wilson
Priority	Medium

md5: a6b58a302d9f3378fd044307df8fc61a

Issue Description:

From the ABI Stability manifesto:

The runtime is also responsible for lazily creating new type metadata entries at run time, either for generic type instantiations or for resilient constructs. Library evolution in general introduces a whole new category of needs from the runtime by making data and metadata more opaque, requiring interaction to be done through runtime APIs. Additionally, ownership semantics may require new runtime APIs or modifications to existing APIs. These new runtime needs are still under investigation.

This issue tracks the completion of those investigations.

[bob-wilson]

@swift-ci create

[rjmccall]

There is no point in tracking this so broadly. Individual resilience tasks will require runtime support, but the changes have no general inter-relationship.

[bob-wilson]

Since we're tracking this on the ABI Stability dashboard, I'd like to keep this open for now. I agree that it's overly broad.

[bob-wilson]

At this point, I have to agree with John. We've split out a new "Ownership" section on the ABI dashboard, and we will track any runtime changes related to ownership along with the specific features listed there. There are still some things left to do for library evolution but I'm not aware of any significant runtime changes that would make sense to track separately here. Let's close this one.