<?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 Z.modulemap</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>1b3b69fb - Warning for framework include violation from Headers to PrivateHeaders</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/Modules/Inputs/framework-public-includes-private/flat-header-path/Z.modulemap#1b3b69fb</link>
        <description>Warning for framework include violation from Headers to PrivateHeadersFramework vendors usually layout their framework headers in thefollowing way:Foo.framework/Headers -&gt; &quot;public&quot; headersFoo.framework/PrivateHeader -&gt; &quot;private&quot; headersSince both headers in both directories can be found with #import&lt;Foo/some-header.h&gt;, it&apos;s easy to make mistakes and include headers inFoo.framework/PrivateHeader from headers in Foo.framework/Headers, whichusually configures a layering violation on Darwin ecosystems. One of theproblem this causes is dep cycles when modules are used, since it&apos;s verycommon for &quot;private&quot; modules to include from the &quot;public&quot; ones; addingan edge the other way around will trigger cycles.Add a warning to catch those cases such that:./A.framework/Headers/A.h:1:10: warning: public framework header includes private framework header &apos;A/APriv.h&apos;#include &lt;A/APriv.h&gt;         ^rdar://problem/38712182llvm-svn: 335542

            List of files:
            /llvm-project-15.0.7/clang/test/Modules/Inputs/framework-public-includes-private/flat-header-path/Z.modulemap</description>
        <pubDate>Mon, 25 Jun 2018 22:24:17 +0000</pubDate>
        <dc:creator>Bruno Cardoso Lopes &lt;bruno.cardoso@gmail.com&gt;</dc:creator>
    </item>
</channel>
</rss>
