: The focus is now on the action (the loop) rather than the technical type name.
However, Elias has to be careful. As some developers have discovered, using auto without specifying it as a reference (like auto& ) can sometimes lead to the compiler making a of the data instead of just looking at the original, which can cause performance issues or bugs in "convenience gone wrong" scenarios. Convenience Gone Wrong: A C++ auto Story
Imagine a developer, Elias, working on a complex piece of software. He needs to iterate through a list of data. Without auto , he has to write out a massive, intimidating type name just to get started: std::vector >::iterator it = accounts.begin(); It’s long, easy to mistype, and makes the actual logic of the code hard to see. auto*used
By using auto , Elias’s code becomes:
: Unlike some other languages, auto in C++ is still strictly typed; it isn't a "guess," but a precise calculation by the compiler during the build process. : The focus is now on the action
Elias decides to use the auto keyword introduced in C++11 . By writing auto it = accounts.begin(); , he tells the compiler, "You already know what accounts.begin() returns, so just make it that type".
: If Elias later changes the data structure from a vector to a list , he doesn't have to manually update every single type declaration; the auto keyword handles it automatically. Convenience Gone Wrong: A C++ auto Story Imagine
Here is a short story of how auto is typically used to simplify a developer's life: The "Auto" Story: From Clutter to Clarity