-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[sourcekitd] Report entities that are implicitly @objc as @objc in the index request responses for compatibility #22793
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
@swift-ci please smoke test |
8eed065
to
5702681
Compare
@swift-ci please smoke test |
5702681
to
ec064e6
Compare
@swift-ci please test and merge |
@swift-ci test and merge |
@swift-ci test OS X |
Build failed |
…index request responses for compatibility Members of an @objcMembers context previous had implicit @objc attributes, but now don't (possibly because of the request evaluator changes?). This updates the output of sourcekitd's 'index' request to act as if they still had implicit @objc attributes on them for compatibility. Resolves rdar://problem/48140265
ec064e6
to
7680cc6
Compare
@swift-ci test and merge |
@Swift-C test |
@swift-ci please smoke test Linux |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can sourcekit call isObjC() instead of checking for the presence of the attribute directly? In the future more “implicitly added” attributes will likely go away.
The code change here updates sourcekitd to call |
E.g. Members of an @objcMembers context previous had implicit @objc attributes but now don't (possibly because of the request evaluator changes?). This updates the output of sourcekitd's 'index' request to act as if they still had implicit @objc attributes on them for compatibility.
Resolves rdar://problem/48140265