<div dir="ltr">On Wed, Nov 9, 2022 at 11:23 AM Brian Goetz <<a href="mailto:brian.goetz@oracle.com">brian.goetz@oracle.com</a>> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>what I'm saying is that we should warn when we
detect there is a *possibility* of a problem, rather than having to
prove that there *will be* a problem. <br></div></blockquote><div><br></div><div>Totally agree... we can allow false positives but definitely not false negatives. That's what allows a programmer to say "I've eliminated all the warnings and so now I KNOW this code can't cause a 'this' escape problem".</div><br><div>As you pointed out, since we can't assume anything about "alien" code, any clever tricks to eliminate false positives are limited to what we can accomplish by analyzing a single source file. Other than that, which false positives we want to hunt down and eliminate is just a standard trade-off between effort required and value provided.</div></div><div><div><br></div></div><div>I'll try to come up with a concrete but simple starting point. We can then discuss whether & how it should be more clever re: false positives.<br></div><div><br></div><div>Thanks,<br></div><div>-Archie<br></div><br>-- <br><div dir="ltr" class="gmail_signature">Archie L. Cobbs<br></div></div>