forked from OSchip/llvm-project
74f02347ca
Under this defect resolution, the injected-class-name of a class or class template cannot be used except in very limited circumstances (when declaring a constructor, in a nested-name-specifier, in a base-specifier, or in an elaborated-type-specifier). This is apparently done to make parsing easier, but it's a pain for us since we don't know whether a template-id using the injected-class-name is valid at the point when we annotate it (we don't yet know whether the template-id will become part of an elaborated-type-specifier). As a tentative resolution to a perceived language defect, mem-initializer-ids are added to the list of exceptions here (they generally follow the same rules as base-specifiers). When the reference to the injected-class-name uses the 'typename' or 'template' keywords, we permit it to be used to name a type or template as an extension; other compilers also accept some cases in this area. There are also a couple of corner cases with dependent template names that we do not yet diagnose, but which will also get this treatment. llvm-svn: 292518 |
||
|---|---|---|
| .. | ||
| CMakeLists.txt | ||
| ParseAST.cpp | ||
| ParseCXXInlineMethods.cpp | ||
| ParseDecl.cpp | ||
| ParseDeclCXX.cpp | ||
| ParseExpr.cpp | ||
| ParseExprCXX.cpp | ||
| ParseInit.cpp | ||
| ParseObjc.cpp | ||
| ParseOpenMP.cpp | ||
| ParsePragma.cpp | ||
| ParseStmt.cpp | ||
| ParseStmtAsm.cpp | ||
| ParseTemplate.cpp | ||
| ParseTentative.cpp | ||
| Parser.cpp | ||
| RAIIObjectsForParser.h | ||