blocks:

• SR-257 Resilient value type support -- umbrella bug

is blocked by:

• SR-269 Implement ResilienceDomain abstraction

is duplicated by:

• SR-3911 Evaluate ABI impact of going from opaque layouts to freezing the layout for performance

Issue Description:

We wish to express that a type was formerly resilient, but became fixed layout. This requires adding an optional availability annotation to @_fixed_layout and plumbing it through to serialization.

The new attribute has the following semantic consequences:

• At the SIL level, types are still passed and returned indirectly if they were ever resilient – this ensures that changing the deployment version does not change the SIL type lowering of function types, since doing that would require generating multiple entry points for functions that reference conditinally-fixed-layout value types

• IRGen however can make assumptions about fixed layout types if the deployment target is at least that of the type

The isResilient() check in NominalTypeDecl will be extended to take a deployment target version too. SIL will not use this, but IRGen will.