[concurrency] Implement protocol witness thunking in SILGen for @execution(caller)/@execution(concurrent). #80622
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@swift-ci smoke test |
…ution(caller)/@execution(concurrent). This involved cleaning up and generalizing the work from f245389. I followed the same approach: hide the implicit parameter while we run things through translateArgument and friends and then put it back in manually. As an additional benefit, I think I found a good place to put FunctionIsolation onto lowered AnyFunctionTypes that will not cause cycles in the evaluator since it is done in TypeLowering. rdar://148785846
gottesmm
force-pushed
the
pr-9c92d645ac34f929bbaf39f2f26aa2e3e3acf5cb
branch
from
10dd745 to
04b845c
Compare
|
@swift-ci smoke test |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This involved cleaning up and generalizing the work from f245389. I followed the same approach: hide the implicit parameter while we run things through translateArgument and friends and then put it back in manually.
As an additional benefit, I think I found a good place to put FunctionIsolation onto lowered AnyFunctionTypes that will not cause cycles in the evaluator since it is done in TypeLowering.
rdar://148785846