-
Notifications
You must be signed in to change notification settings - Fork 11.8k
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
Clang C++20 Feature: Declarations and where to find them (P1787) #54150
Comments
@llvm/issue-subscribers-c-20 |
I'm adding DR status in Clang's implementation staus page (#68846). Do you think we should specially list P1787R6 (which is effectively a DR) in that page or track resolved issues in the page for CWG issues? |
CC @Endilll who has also been working on conformance tests in this area. Personally, I think it's more helpful to track the individual resolved issues than it is to track status of the omnibus paper fixing them; I expect the paper's status will be |
Here is status for tests (checkbox) and availability (in parentheses) in the order P1787R6 describes them. N/A are marked as having tests, since no work is due for them. I'm also listing only defect reports, omitting unresolved Core issues. Definitions
Lookup completeness
Complete-class context
Declaration matching
ModulesNo defect reports in this section. Parsing
Templates
|
While there are some more currently under review, I put this paper on hold, until I have more time and a wording expert willing to spend their time to dive into this. As if definitions and lookup completeness sections weren't complicated enough, it gets even worse in subsequent sections. |
@llvm/issue-subscribers-clang-frontend Author: cor3ntin (cor3ntin)
Paper link: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2020/p1787r6.html
This fixes a number of DRs, I think a first order of business would be to understand what changes are actually needed in clang |
Paper link: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2020/p1787r6.html
This fixes a number of DRs, I think a first order of business would be to understand what changes are actually needed in clang
The text was updated successfully, but these errors were encountered: