-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[Distributed] Strip marker protocols from distributed thunks and accessible functions #41871
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Distributed] Strip marker protocols from distributed thunks and accessible functions #41871
Conversation
…unks Distributed thunks loose all of the marker protocols associated with their generic parameters.
…e function generic environments Since marker protocol do not exist at runtime, it's harmful to keep them in a generic environment because they cannot be checked. Resolves: rdar://90293494
…arker protocols are not mangled
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice,:l thank you!
return !protocol->isMarkerProtocol(); | ||
} | ||
return true; | ||
}); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see, nice
@swift-ci please smoke test |
@swift-ci please test macOS platform |
Let's run a full suite just in case. |
Yeah, sounds good 👍 |
CI node died, starting again
@swift-ci please test macOS platform |
and full test runs all good 🥳 |
Since marker protocols do not exist at runtime, let's strip them from mangling of distributed thunks
and generic environments associated with accessible functions.
Resolves: rdar://90293494