Skip to content

[SR-3923] Plan for the evolution of type metadata #46508

Closed
@ematejska

Description

@ematejska
mannequin
Previous ID SR-3923
Radar rdar://problem/31414905
Original Reporter @ematejska
Type Bug
Status Resolved
Resolution Done
Additional Detail from JIRA
Votes 0
Component/s Compiler
Labels Bug, AffectsABI
Assignee None
Priority Medium

md5: 9f8ac371fcbf685d78374b9bcd2fe523

Issue Description:

Ahead of ABI Stability, provide type metadata read/write functions alongside the runtime to interact with metadata, giving some freedom to the underlying structures to grow and change. This effectively makes large portions of metadata opaque.

For those fields that require access to be as efficient as possible (e.g. dynamic casts, calling into witness tables) and the performance hit from going through an intermediary function would be unacceptable, freeze those parts of the metadata representation.

Metadata

Metadata

Assignees

No one assigned

    Labels

    affects ABIFlag: Affects ABIbugA deviation from expected or documented behavior. Also: expected but undesirable behavior.compilerThe Swift compiler itself

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions