<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On Apr 8, 2013, at 2:19 PM, John McCall <<a href="mailto:rjmccall@apple.com">rjmccall@apple.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="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;">On Apr 8, 2013, at 12:42 PM, Erik Verbruggen <<a href="mailto:erik.verbruggen@me.com">erik.verbruggen@me.com</a>> wrote:<br><blockquote type="cite">Pardon my ignorance, but why a warning? Or to rephrase it: why could this be problematic at all to fail with -Werror?<br></blockquote><br>There's no good reason to use "auto" in a situation where it will always infer as "id". People should either explicitly provide a more specific type, in which case uses of the value will actually be meaningfully type-checked, or they should type "id", which is shorter.<br></div></blockquote></div><div><br></div>… and it's not an error because this could legitimately happen during template instantiation, where we suppress the warning.<div><br><div><span class="Apple-tab-span" style="white-space:pre"> </span>- Doug</div><div><br></div></div></body></html>