Sema: Fix local property wrappers on constructor [6.1] #78528
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
Fixes rdar://problem/142443421.
hborla
approved these changes
Jan 9, 2025
|
@swift-ci Please test |
…n external property wrapper The check to see whether argument matches the parameter exactly causes two problems: prevents projected value initialized injection; and, if there are multiple parameters with property wrappers, would apply incorrect wrapper to other locations because the wrapper application index wasn't incremented. Resolves: rdar://140282980
|
@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.
6.1 cherry-pick of #78470
Description: Some new assertions were added to ensure that property wrappers are recorded in the right places, which introduced a crash in a case that was not previously covered by the test suite.
Origination: Regression was caused by the SolverTrail refactoring which is new in 6.1.
Risk: Low.
Reviewed by: @xedin
Radar: rdar://141961300