<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Mar 27, 2012, at 12:21 PM, Nick Lewycky wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Ping!<div><br></div><div>Argyrios, you made the change in this value from 35 to 37. Could you please take a look?</div></blockquote><div><br></div><div>I'll take a look but I didn't just change the value from 35 to 37, this was the full change:</div><div><br></div><div><div>-// CHECK-CC1: ObjCPropertyDecl:{ResultType double}{TypedText prop4} (35)</div><div><div>[...]</div><div>+// CHECK: ObjCIvarDecl:{ResultType double}{TypedText prop4} (37)</div></div><div><br></div><div>notice that, after the change, autocomplete shows the ivar instead of the property.</div></div><br><blockquote type="cite"><div><span style="font-family:Times;font-size:medium"><font face="arial"><br></font></span></div><div><span style="font-family:Times;font-size:medium"><font face="arial">Nick</font></span></div>
<div><span style="font-family:Times;font-size:medium"><font face="arial"><br></font></span><div class="gmail_quote">On 23 March 2012 22:12, Nick Lewycky <span dir="ltr"><<a href="mailto:nlewycky@google.com">nlewycky@google.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">LookupVisibleDecls does redundant work which was caught by my new assertion (see PR12339) but upon further investigation we found that it's also buggy in some cases. Two new testcases are included.<div>
<br></div><div>The attached patch works by adding a new iterator on DeclContext which exposes all decls that would be visible through DC->lookup() as an iterator, then LookupVisibleDecls just iterates through those. The fix also allows us to delete some code in code completion.</div>
<div><br></div><div>There is one form of fallout which I don't understand, and I need review for this. In one Objective-C test, the autocomplete priority changed from 37 to 35. It's not clear to me whether that's a bug fixed or a bug introduced, and I'd appreciate some help understanding why prop4 should have been getting the 2-point penalty in test/Index/complete-synthesized.m (and not, say, prop2 which actually is in the base class). It looks from the commit log like that number might not actually be important.</div>
<div><br></div><div>Please review! This patch has Richard Smith approval, subject to the change to the objective-c tests being approved by somebody else.</div><span class="HOEnZb"><font color="#888888"><div><br></div><div>
Nick</div>
</font></span></blockquote></div><br></div>
<span><pr12339-2.patch></span>_______________________________________________<br>cfe-commits mailing list<br><a href="mailto:cfe-commits@cs.uiuc.edu">cfe-commits@cs.uiuc.edu</a><br>http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits<br></blockquote></div><br></body></html>