forked from OSchip/llvm-project
990668b7d0
DR407, the C++ standard doesn't really say how this should work. Here's what we do (which is consistent with DR407 as far as I can tell): * When performing name lookup for an elaborated-type-specifier, a tag declaration hides a typedef declaration that names the same type. * When performing any other kind of lookup, a typedef declaration hides a tag declaration that names the same type. In any other case where lookup finds both a typedef and a tag (that is, when they name different types), the lookup will be ambiguous. If lookup finds a tag and a typedef that name the same type, and finds anything else, the lookup will always be ambiguous (even if the other entity would hide the tag, it does not also hide the typedef). llvm-svn: 252959 |
||
|---|---|---|
| .. | ||
| analyzer | ||
| demo | ||
| OpenProjects.html | ||
| UniversalDriver.html | ||
| builtins.py | ||
| carbon-compile.png | ||
| clang_video-05-25-2007.html | ||
| clang_video-07-25-2007.html | ||
| comparison.html | ||
| compatibility.html | ||
| content.css | ||
| cxx_compatibility.html | ||
| cxx_dr_status.html | ||
| cxx_status.html | ||
| diagnostics.html | ||
| favicon.ico | ||
| feature-compile1.png | ||
| feature-compile2.png | ||
| feature-memory1.png | ||
| features.html | ||
| get_involved.html | ||
| get_started.html | ||
| hacking.html | ||
| index.html | ||
| libstdc++4.4-clang0x.patch | ||
| libstdc++4.6-clang11.patch | ||
| libstdc++4.7-clang11.patch | ||
| make_cxx_dr_status | ||
| menu.css | ||
| menu.html.incl | ||
| related.html | ||
| robots.txt | ||
