[AST] Introduce Argument::implicitInOut
#60438
Merged
Conversation
This file contains hidden or 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
This conversion should already be handled by `buildSelfReference`.
This will allow us to abstract away the creation of InOutExpr for bits of code synthesis.
This allows us to more easily propagate inout information to it, which will become a necessity once InOutExpr is removed.
|
@swift-ci please 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.
The first step on a long road towards removing InOutExpr/InOutType. Introduce
Argument::implicitInOut, and use it to factor outInOutExprcreation for a bunch of code synthesis logic. This will eventually becomeArgument::inoutand will just store the expression along with an "is inout" bit.