You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The optimizer makes assumptions about layout equivalence. See canUnsafeCastStruct/Tuple/Enum. This code should be centralized in an ABI spec (see SR-3730). But we also need to make sure this code honors resilience boundaries. Currently it just runs over the list of stored properties on the type.
After reviewing this, we have decided not to tackle changes for this in Swift 5. We'll lose some optimization opportunities for fragile generic structs that are published with the old algorithm, but we can still adjust the algorithm for future compiler versions.
Additional Detail from JIRA
md5: a21fe6ef95bd4b08859b864fa7a24dc9
Issue Description:
This bug is tracking investigating how to most efficiently lay out partially-opaque aggregates before ABI Stability is achieved.
The text was updated successfully, but these errors were encountered: