<html>
    <head>
      <base href="https://bugs.llvm.org/">
    </head>
    <body><span class="vcard"><a class="email" href="mailto:richard-llvm@metafoo.co.uk" title="Richard Smith <richard-llvm@metafoo.co.uk>"> <span class="fn">Richard Smith</span></a>
</span> changed
          <a class="bz_bug_link 
          bz_status_RESOLVED  bz_closed"
   title="RESOLVED INVALID - Inconsistent error message in "expected unqualified-id""
   href="https://bugs.llvm.org/show_bug.cgi?id=46329">bug 46329</a>
          <br>
             <table border="1" cellspacing="0" cellpadding="8">
          <tr>
            <th>What</th>
            <th>Removed</th>
            <th>Added</th>
          </tr>

         <tr>
           <td style="text-align:right;">Status</td>
           <td>NEW
           </td>
           <td>RESOLVED
           </td>
         </tr>

         <tr>
           <td style="text-align:right;">Resolution</td>
           <td>---
           </td>
           <td>INVALID
           </td>
         </tr></table>
      <p>
        <div>
            <b><a class="bz_bug_link 
          bz_status_RESOLVED  bz_closed"
   title="RESOLVED INVALID - Inconsistent error message in "expected unqualified-id""
   href="https://bugs.llvm.org/show_bug.cgi?id=46329#c4">Comment # 4</a>
              on <a class="bz_bug_link 
          bz_status_RESOLVED  bz_closed"
   title="RESOLVED INVALID - Inconsistent error message in "expected unqualified-id""
   href="https://bugs.llvm.org/show_bug.cgi?id=46329">bug 46329</a>
              from <span class="vcard"><a class="email" href="mailto:richard-llvm@metafoo.co.uk" title="Richard Smith <richard-llvm@metafoo.co.uk>"> <span class="fn">Richard Smith</span></a>
</span></b>
        <pre>We intentionally change and improve our diagnostics between Clang revisions,
including intentionally suppressing later errors after an earlier diagnostic
for a particular issue, so I would imagine that you're going to see a lot of
false positives by this method for every real bug that you find.

If you're going to go ahead with looking for more bugs by this technique, I'd
ask that you check to see whether each change looks like a bug before reporting
it. For a parse error such as this one, if Clang changes to produce better
diagnostics (as in this case), we generally won't be interested in a bug
report. If you're not sure whether a change is a bug or not, please mention
that in the bug report so we're not left to puzzle out why you think there's a
problem.

Finally, please understand if your bug reports get marked INVALID with very
little explanation in future. I'm marking this one invalid now, because the new
behavior is an improvement.</pre>
        </div>
      </p>


      <hr>
      <span>You are receiving this mail because:</span>

      <ul>
          <li>You are on the CC list for the bug.</li>
      </ul>
    </body>
</html>