Skip to content

[Index/USRGeneration] Make sure that ObjC properties in categories also get namescoped properly for USR generation #887

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

Conversation

akyrtzi
Copy link

@akyrtzi akyrtzi commented Mar 8, 2020

If the property is in a category that has module names from external_declaration property, make sure they are included in the USR.

rdar://59897320

…so get namescoped properly for USR generation

If the property is in a category that has module names from external_declaration property, make sure they are included in the USR.

rdar://59897320
@akyrtzi
Copy link
Author

akyrtzi commented Mar 8, 2020

@swift-ci test OS X platform

@akyrtzi akyrtzi merged commit 466d67a into swiftlang:apple/stable/20200108 Mar 8, 2020
@akyrtzi akyrtzi deleted the usr-generation-objc-prop-external branch March 8, 2020 20:41
swift-ci pushed a commit to swiftlang/swift that referenced this pull request Mar 10, 2020
… the clang side

This is a Swift-side test case for swiftlang/llvm-project#887
Ensures Swift and Clang are in-sync on the USRs for exported properties.
akyrtzi added a commit to swiftlang/swift that referenced this pull request Mar 12, 2020
… the clang side

This is a Swift-side test case for swiftlang/llvm-project#887
Ensures Swift and Clang are in-sync on the USRs for exported properties.
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.

1 participant