Previous: Back To Stack Overflow, And Look What's Happened
Next: Fringe: The Bullet That Saved The World
It has begun:
There is no such thing as "an auto"!
See, this is why I disagreed with the proposal to add this syntactic sugar.
Ahh but this is far more than syntactic sugar I use auto now more often than not, having left my fears of overuse and abuse well behind now.
Annoying this may be, but if it's a newbie's misunderstanding then so be it. Long live auto!
typedefs exist to replace concrete types with semantic-looking equivalents, making switching the concrete types easy — auto on the other hand is prone to a type changing without you even really realising it, if you make some trivial change in code elsewhere (say, a function return type, or perhaps you add a new function that by accident is a better match for some call than the function you meant to use). Seems to me that that is worse for maintainability!