<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">It would, so it’s better than nothing, but it would disappear as soon as the un-intentional bug appears. But, as Kevin stated, there are too many good used of shadowing to suffer a warning.<div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 05 Dec 2015, at 00:20, Stephen Celis <<a href="mailto:stephen.celis@gmail.com" class="">stephen.celis@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">On Fri, Dec 4, 2015 at 5:59 PM, David Hart <span dir="ltr" class=""><<a href="mailto:david@hartbit.com" target="_blank" class="">david@hartbit.com</a>></span> wrote:<br class=""><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class="">Stephen, as previously stated by Rudolf, his real-world example would not trigger such a warning because the title local variable no longer exists and therefore no longer shadows the instance property.</div></blockquote><div class=""><br class=""></div><div class="">Wouldn't the warning trigger prior to refactoring and therefore be more apparent during such a removal?</div></div></div></div>
</div></blockquote></div><br class=""></div></body></html>