Skip to content

Improve compatibility layer for KeyPathPropertyComponentSyntax #2052

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

ahoppen
Copy link
Member

@ahoppen ahoppen commented Aug 11, 2023

The rename of identifier -> declName was not correct in KeyPathPropertyComponentSyntax because we also chagned its type from TokenSyntax to DeclReferenceExprSyntax.

Instead, provide two hand-written compatibility properties that transparently access the DeclReferenceExprSyntax.

The rename of `identifier` -> `declName` was not correct in `KeyPathPropertyComponentSyntax` because we also chagned its type from `TokenSyntax` to `DeclReferenceExprSyntax`.

Instead, provide two hand-written compatibility properties that transparently access the `DeclReferenceExprSyntax`.
@ahoppen ahoppen requested a review from bnbarham August 11, 2023 22:32
@ahoppen
Copy link
Member Author

ahoppen commented Aug 11, 2023

@swift-ci Please test

Copy link
Contributor

@bnbarham bnbarham left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IIUC there were a few that we changed to declReferenceExpr - does that apply to any of the others?

@ahoppen
Copy link
Member Author

ahoppen commented Aug 14, 2023

All of the other places were the arguments of underscored attributes, which I don’t expect many clients to use.

@ahoppen ahoppen merged commit f0c746c into swiftlang:main Aug 14, 2023
@ahoppen ahoppen deleted the ahoppen/key-path-property-compatibility branch August 14, 2023 18:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants