[SILGen] Handle struct projectedValue
in struct property wrapper that has mutating setter
#81232
+39
−0
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.
Resolves #81021
When the
projectedValue
is a struct within a struct property wrapper that has a mutating setter, and we use the property wrapper as a function parameter, theprojectedValue
becomes an Rvalue and does not have an address.This issue does not occur if the property wrapper is a class, or if the projectedValue itself is a class.
Previously, we did not handle this case, which led to an assertion failure in the following code:
Since it is not an address, we could not treat it the same as the borrow cases.
Therefore, we needed to handle this scenario differently.