<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=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jun 29, 2016, at 2:54 AM, Douglas Gregor <<a href="mailto:dgregor@apple.com" class="">dgregor@apple.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">This seems very related to the near-miss checking I mentioned in my other reply to Austin. </span></div></blockquote></div><br class=""><div class="">Yeah. Well, if we get the error message. It’s better than nothing. I don’t know the specifics about compilers and rules and what not. But it seems to me it would be opening an exception just for that specific case. And that might be something that would make the compiler rules more complex. So if we don’t get the message, we get more consistency in the rules, but on the other hand we make it easier for people to accidentally get unexpected behaviour. </div></body></html>