<?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 p5-implicit.cpp</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>aa6ce341 - Fix tracking of whether a destructor would be deleted.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/CXX/special/class.dtor/p5-implicit.cpp#aa6ce341</link>
        <description>Fix tracking of whether a destructor would be deleted.I&apos;ve been unable to find any cases whose behavior is actually changed by this,but only because an implicitly deleted destructor also results in it beingimpossible to have a trivial (non-deleted) copy constructor, which the placewhere this really matters (choosing whether to pass a class in registers)happens to also check.llvm-svn: 313948

            List of files:
            /llvm-project-15.0.7/clang/test/CXX/special/class.dtor/p5-implicit.cpp</description>
        <pubDate>Fri, 22 Sep 2017 01:04:22 +0000</pubDate>
        <dc:creator>Richard Smith &lt;richard-llvm@metafoo.co.uk&gt;</dc:creator>
    </item>
</channel>
</rss>
