<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=""><div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><div class=""><blockquote type="cite" class="">I’d love to see examples where using auto substantially hurts readability so we could debate them.<br class=""></blockquote></div></div></div></div></blockquote>I once saw a RefPtr<Something> changed to auto in some generated code where it was unclear what the return type was. For at least one generated instance the return type was Something* that needed a reference kept alive by the caller, so this change caused a subtle use-after-free bug. See <a href="https://trac.webkit.org/changeset/201345" class="">https://trac.webkit.org/changeset/201345</a></div><div><br class=""></div><div>Also when we change what a return type is but there are call sites that use auto, we may miss checking to see if everything is ok at a call site that compiles successfully even though it has different meaning.</div><div><br class=""></div><div>I’ll admit auto has grown on me quite a bit since I wrote <a href="https://lists.webkit.org/pipermail/webkit-dev/2014-January/026000.html" class="">https://lists.webkit.org/pipermail/webkit-dev/2014-January/026000.html</a></div><div><br class=""></div></body></html>