vendor/clang/clang-r84119

1 files changed, 4 insertions, 6 deletions

diff --git a/www/OpenProjects.html b/www/OpenProjects.html
index c0ee9989f2b2..cdf31218bbeb 100644
--- a/www/OpenProjects.html
+++ b/www/OpenProjects.html
@@ -82,12 +82,10 @@ job, but there are lots of little pieces that can be picked off and implemented.
 <ul>
   <li>Fix bugs: there are a number of XFAIL'd test cases in Clang's repository (particularly in the CXX subdirectory). Pick a test case and fix Clang to make it work!</li>
   <li>Write tests: the CXX test subdirectory in Clang's repository has placeholders for tests of every paragraph in the C++ standard. Pick a paragraph, write a few tests, and see if they work! Even if they don't we'd still like the new tests (with XFAIL'd) so that we know what to fix.</li>
-  <li>Type-checking for explicit conversions: currently follows C semantics, not C++ semantics.</li>
-  <li>Qualified member references: C++ supports qualified member references such as <code>x-&gt;Base::foo</code>, but Clang has no parsing or semantic analysis for them.</li>
- <li>Parsing and AST representations of friend classes and functions</li>
-  <li>Explicit calls to destructors and pseudo-destructor expressions (<code>x.~X()</code>).</li>
-  <li>AST representation for implicit C++ conversions: implicit conversions that involve non-trivial operations (e.g., invoking a user-defined conversion function, performing a base-to-derived or derived-to-base conversion) need explicit representation in Clang's AST.</li>
-  <li>Improved diagnostics for overload resolution failures: after an overload resolution failure, we currently print out the overload resolution candidates. We should also print out the reason that each candidate failed, e.g., "too few arguments", "too many arguments", "cannot initialize parameter with an lvalue of type 'foo'", etc.</li>
+  <li>Parsing and semantic analysis for using declarations in classes</li>
+  <li>Inherited conversion functions</li>
+  <li>Improved diagnostics for overloading failures and ambiguities</li>
+  <li>Improved template error messages, e.g., with more informative backtraces</li>
 </ul>
   
 Also, see the <a href="cxx_status.html">C++ status report page</a> to