<?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 module.modulemap</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>25d50758 - [modules] Add support for #include_next.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/Modules/Inputs/include_next/x/module.modulemap#25d50758</link>
        <description>[modules] Add support for #include_next.#include_next interacts poorly with modules: it depends on where in the list ofinclude paths the current file was found. Files covered by module maps are notfound in include search paths when building the module (and are not found ininclude search paths when @importing the module either), so this isn&apos;t reallymeaningful. Instead, we fake up the result that #include_next *should* havegiven: find the first path that would have resulted in the given file beingpicked, and search from there onwards.llvm-svn: 220177

            List of files:
            /llvm-project-15.0.7/clang/test/Modules/Inputs/include_next/x/module.modulemap</description>
        <pubDate>Mon, 20 Oct 2014 00:15:49 +0000</pubDate>
        <dc:creator>Richard Smith &lt;richard-llvm@metafoo.co.uk&gt;</dc:creator>
    </item>
</channel>
</rss>
