<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1251"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">On Jan 3, 2014, at 10:11 AM, Alexey Proskuryakov <<a href="mailto:ap@webkit.org">ap@webkit.org</a>> wrote:<br><div><br class="Apple-interchange-newline"><blockquote type="cite"><meta http-equiv="Content-Type" content="text/html charset=koi8-r"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">I'm not Geoff, yet I'd like to offer my perspective on the specific examples you provided.<br><div><br><div><div>03 ÿíâ. 2014 ã., â 4:12, Antti Koivisto <<a href="mailto:koivisto@iki.fi">koivisto@iki.fi</a>> íàïèñàë(à):</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>auto& cell = toRenderTableCell(*renderer); // right</div><div>RenderTableCell& cell = toRenderTableCell(*renderer); // wrong</div></blockquote><div><br></div><div>I can't agree with this example. With auto, I don't know if it's a raw pointer, a reference, or a smart pointer (we have toXXX functions that return all of those). I also cannot Cmd+click on anything to go to the class definition, and when I Cmd-click on toRenderTableCell, I presumably get into some unreadable macro.</div><div><br></div><div>Overall, auto makes the code very opaque here.</div></div></div></div></blockquote></div><br><div>I agree. I think use of auto makes code you’re unfamiliar with much harder to follow, and makes getting to the type declaration one more Command-click away. Better tools integration would help; if I could hover over the “auto” had have Xcode show me, in a tooltip, what type the compiler will infer, then I’d be more willing to see wider use of auto.</div><div><br></div><div>Simon</div><div><br></div></body></html>