[TaskLocal] Carry access control modifiers into synthesized property #73475
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 is to make sure the expanded macros can properly work with availability and values which may require availability
|
@swift-ci please smoke test |
10 tasks
MaxDesiatov
approved these changes
May 7, 2024
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 new approach to
@TaskLocalwith macros missed to carry to the synthesized property the access control modifiers. which can be source breaking, accidentally making a $property internal when it must have been public or private etc.Along the way, cleanup how we do this pattern, and avoid forming strings to create access control in the macro and fix it in other uses of this pattern.
Resolves rdar://127498720