<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in cxx20-using-enum.cpp</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>b2d0c16e - [clang] p1099 using enum part 2</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/SemaCXX/cxx20-using-enum.cpp#b2d0c16e</link>
        <description>[clang] p1099 using enum part 2This implements the &apos;using enum maybe-qualified-enum-tag ;&apos; part of1099. It introduces a new &apos;UsingEnumDecl&apos;, subclassed from&apos;BaseUsingDecl&apos;. Much of the diff is the boilerplate needed to get thenew class set up.There is one case where we accept ill-formed, but I believe this ismerely an extended case of an existing bug, so consider itorthogonal. AFAICT in class-scope the c++20 rule is that no 2 usingdecls can bring in the same target decl ([namespace.udecl]/8). But wealready accept:struct A { enum { a }; };struct B : A { using A::a; };struct C : B { using A::a;using B::a; }; // same enumeratorthis patch permits mixtures of &apos;using enum Bob;&apos; and &apos;using Bob::member;&apos; in the same way.Differential Revision: https://reviews.llvm.org/D102241

            List of files:
            /llvm-project-15.0.7/clang/test/SemaCXX/cxx20-using-enum.cpp</description>
        <pubDate>Wed, 05 May 2021 15:55:02 +0000</pubDate>
        <dc:creator>Nathan Sidwell &lt;nathan@acm.org&gt;</dc:creator>
    </item>
</channel>
</rss>
