<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Yeah would be great if you could implement a prototype, and then I could check it on a bunch of codebases.<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Sep 5, 2018, at 11:20 AM, Kristóf Umann <<a href="mailto:dkszelethus@gmail.com" class="">dkszelethus@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="gmail_quote"><br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word;line-break:after-white-space" class=""><div class=""><div class=""></div><div class="">Another hack I was thinking about:</div><div class=""><br class=""></div><div class=""> - Check *syntactically* whether there is an *unguarded* access to uninitialized fields in equality/assignment/destructor operators.</div><div class="">Or maybe unguarded access in general.</div><div class="">This is checkable syntactically and provides a fairly strong indicator of a bug.</div><div class=""><br class=""></div><div class="">I wish we had dataflow for that, but we don’t =/</div><br class=""></div></div></blockquote><div class="">I like this a lot. This could reduce the amount of reports greatly. Thanks!<br class=""></div></div></div>
</div></blockquote></div><br class=""></body></html>