Skip to content

Conversation

@DougGregor
Copy link
Member

@DougGregor DougGregor commented Jul 28, 2021

Add implicit conformance of structural types to Sendable as appropriate:

  • A tuple type is Sendable when its element types are Sendable
  • A metatype type is Sendable
  • A function type is Sendable if it is @Sendable, thin, or C
  • A builtin type is always Sendable

Implements rdar://76836578.

Azoy and others added 3 commits July 27, 2021 23:49
…rmance.

Give BuiltinProtocolConformance a generic signature, which can be used to
describe the generic parameters used within the builtin conformance, e.g.,
`<T1, T2, T3>` for a tuple type `(T1, T2, T3)`. Also store the
conditional requirements as trailing objects, requiring them to be
precomputed by whatever builds the conformances. Together, this means
that builtin protocol conformances act like normal conformances with
respect to conditional requirements and substitutions: they will be
defined generically, then a specialized conformance will be layered on
top to provide the substitutions.
Add implement conformance of structural types to Sendable as appropriate:
* A tuple type is Sendable when its element types are Sendable
* A metatype type is Sendable
* A function type is Sendable if it is @sendable, thin, or C
* A builtin type is always Sendable

Implements rdar://76836578.
@DougGregor
Copy link
Member Author

@swift-ci please smoke test

…ol".

Now that we synthesize conformances for structural types to `Sendable`,
we can just do this check.
@DougGregor
Copy link
Member Author

@swift-ci please smoke test

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants