Skip to content

Conversation

@DougGregor
Copy link
Member

When a distributed-actor-isolated witness is provided for a
non-distributed-actor-isolated requirement, always hop to the
distributed thunk.

While here, mark distributed thunks as being final, to ensure that
we always statically call them vs. trying to retrieve them from the
vtable (since they aren't in the vtable).

When a distributed-actor-isolated witness is provided for a
non-distributed-actor-isolated requirement, always hop to the
distributed thunk.

While here, mark distributed thunks as being `final`, to ensure that
we always statically call them vs. trying to retrieve them from the
vtable (since they aren't in the vtable).
@DougGregor
Copy link
Member Author

@swift-ci please smoke test

@ktoso ktoso added the distributed Feature → concurrency: distributed actor label Jun 16, 2022
Copy link
Contributor

@ktoso ktoso left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks!

@ktoso ktoso merged commit 74503f0 into swiftlang:main Jun 17, 2022
@DougGregor DougGregor deleted the distributed-witness-mark-2 branch June 17, 2022 05:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

distributed Feature → concurrency: distributed actor

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants