<html>
    <head>
      <base href="http://llvm.org/bugs/" />
    </head>
    <body><span class="vcard"><a class="email" href="mailto:jordan_rose@apple.com" title="Jordan Rose <jordan_rose@apple.com>"> <span class="fn">Jordan Rose</span></a>
</span> changed
              <a class="bz_bug_link 
          bz_status_RESOLVED  bz_closed"
   title="RESOLVED INVALID - False positive "potential leak of an object" with wrapper reset method"
   href="http://llvm.org/bugs/show_bug.cgi?id=15846">bug 15846</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;">CC</td>
           <td>
                
           </td>
           <td>jordan_rose@apple.com
           </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 - False positive "potential leak of an object" with wrapper reset method"
   href="http://llvm.org/bugs/show_bug.cgi?id=15846#c1">Comment # 1</a>
              on <a class="bz_bug_link 
          bz_status_RESOLVED  bz_closed"
   title="RESOLVED INVALID - False positive "potential leak of an object" with wrapper reset method"
   href="http://llvm.org/bugs/show_bug.cgi?id=15846">bug 15846</a>
              from <span class="vcard"><a class="email" href="mailto:jordan_rose@apple.com" title="Jordan Rose <jordan_rose@apple.com>"> <span class="fn">Jordan Rose</span></a>
</span></b>
        <pre>CFStringCreateWithCString could some day do some magic uniquing and return the
same string back. (Seems very reasonable for, say, the empty string.)

More seriously, you have an implementation that's broken in certain edge cases,
and just because this probably isn't one of them today doesn't mean that the
code is really correct. You can always use an assertion instead of a comparison
if you don't want to handle that case.</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>