<?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 static_assert-already-defined.c</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>8da09038 - Improve static_assert/_Static_assert diagnostics</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/Preprocessor/static_assert-already-defined.c#8da09038</link>
        <description>Improve static_assert/_Static_assert diagnosticsOur diagnostics relating to static assertions were a bit confused. Forinstance, when in MS compatibility mode in C (where we acceptstatic_assert even without including &lt;assert.h&gt;), we would failto warn the user that they were using the wrong spelling (even inpedantic mode), we were missing a compatibility warning about using_Static_assert in earlier standards modes, diagnostics for the optionalmessage were not reflected in C as they were in C++, etc.

            List of files:
            /llvm-project-15.0.7/clang/test/Preprocessor/static_assert-already-defined.c</description>
        <pubDate>Wed, 03 Mar 2021 13:44:04 +0000</pubDate>
        <dc:creator>Aaron Ballman &lt;aaron@aaronballman.com&gt;</dc:creator>
    </item>
</channel>
</rss>
