<html>
    <head>
      <base href="http://llvm.org/bugs/" />
    </head>
    <body><span class="vcard"><a class="email" href="mailto:rikka@google.com" title="Kaelyn Takata <rikka@google.com>"> <span class="fn">Kaelyn Takata</span></a>
</span> changed
              <a class="bz_bug_link 
          bz_status_RESOLVED  bz_closed"
   title="RESOLVED FIXED - Incorrect error on undeclared variable use"
   href="http://llvm.org/bugs/show_bug.cgi?id=21656">bug 21656</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>FIXED
           </td>
         </tr></table>
      <p>
        <div>
            <b><a class="bz_bug_link 
          bz_status_RESOLVED  bz_closed"
   title="RESOLVED FIXED - Incorrect error on undeclared variable use"
   href="http://llvm.org/bugs/show_bug.cgi?id=21656#c2">Comment # 2</a>
              on <a class="bz_bug_link 
          bz_status_RESOLVED  bz_closed"
   title="RESOLVED FIXED - Incorrect error on undeclared variable use"
   href="http://llvm.org/bugs/show_bug.cgi?id=21656">bug 21656</a>
              from <span class="vcard"><a class="email" href="mailto:rikka@google.com" title="Kaelyn Takata <rikka@google.com>"> <span class="fn">Kaelyn Takata</span></a>
</span></b>
        <pre>Indeed it was fallout in the form of a code path not covered by any of the
regression tests where a type-dependent TypoExpr node would be seen by a
non-C++ code path that tried to check the expression's type and failed. I've
fixed this case and added a test in r222694.

As an aside, the assertion in ~Sema from r222552 would have been triggered if
asserts were enable, highlighting the fact that a typo had been encountered but
never corrected (i.e. a TypoExpr was created but never diagnosed) and providing
a better indication of what went wrong than the generated error message had. ;)</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>