-
Notifications
You must be signed in to change notification settings - Fork 333
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
Upstream ns_error_domain attribute #1565
Conversation
|
@gribozavr, @DougGregor, I would appreciate your review on this change. |
|
LGTM! @DougGregor could you review & merge? |
|
Thanks for the review. Please don't merge, yet. I think I may have found an issue. I'll mark this as draft while I investigate (tomorrow). |
|
This is ready for review (and merging) now. |
|
I've added an additional test from the upstream code review and rebased against @DougGregor, can you review and merge this? |
|
Hi @DougGregor, we do have commit rights for this branch now, so we can also move ahead on our own. We are still interested in your feedback, though, if you have time. |
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.
I only had the chance to skim this, but it LGTM. Thank you!
This change proactively applies the changes that have been made to ns_error_domain during upstreaming to avoid merge conflicts when the change trickles down. Original changelist description: ns_error_domain can be used by, e.g. NS_ERROR_ENUM, in order to identify a global declaration representing the domain constant. Introduces the attribute, Sema handling, diagnostics, and test case. This is cherry-picked from llvm/llvm-project-staging@a14779f and adapted to updated Clang APIs.
This had been changed during upstreaming of the attribute and needs some updates.
There are two commits in this pull request:
The first commit proactively applies the changes that have been made to
ns_error_domainduring upstreaming to avoid merge conflicts when the change trickles down. This has been reviewed upstream at D84005, but not submitted, yet. If more comments come up for this part, I would apply them to the upstream code review.The second commit adds additional changes for APInotes that have not been reviewed, yet.