<?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>4aafd5f0 - [clang] Remove misleading assertion in FullSourceLoc</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/Modules/Inputs/explicit-build-diags/module.modulemap#4aafd5f0</link>
        <description>[clang] Remove misleading assertion in FullSourceLocD31709 added an assertion was added to `FullSourceLoc::hasManager()` that ensured a valid `SourceLocation` is always paired with a `SourceManager`, and missing `SourceManager` is always paired with an invalid `SourceLocation`.This appears to be incorrect, since clients never cared about constructing `FullSourceLoc` to uphold that invariant, or always checking `isValid()` before calling `hasManager()`.The assertion started failing when serializing diagnostics pointing into an explicit module. Explicit modules don&apos;t have valid `SourceLocation` for the `import` statement, since they are &quot;imported&quot; from the command-line argument `-fmodule-name=x.pcm`.This patch removes the assertion, since `FullSourceLoc` was never intended to uphold any kind of invariants between the validity of `SourceLocation` and presence of `SourceManager`.Reviewed By: arphamanDifferential Revision: https://reviews.llvm.org/D106862

            List of files:
            /llvm-project-15.0.7/clang/test/Modules/Inputs/explicit-build-diags/module.modulemap</description>
        <pubDate>Fri, 06 Aug 2021 12:46:41 +0000</pubDate>
        <dc:creator>Jan Svoboda &lt;jan_svoboda@apple.com&gt;</dc:creator>
    </item>
</channel>
</rss>
