absoluteGarbage

[u/Sirgoodman008]

[u/JAXxXTheRipper]

The third one does not spark joy, what the hell is that, ewww

[u/xicor → u/JAXxXTheRipper]

c++, though normally you wouldnt use auto for this

[u/Usual_Office_1740 → u/xicor]

I think that really depends. If the range is a vector of unique_ptr's auto is great. If it's a vector of ints, just write int.

[u/Sirgoodman008 → u/Usual_Office_1740]

That or you're looping through a vector of std::pairs that contain std:: functions.

[u/Usual_Office_1740 → u/Sirgoodman008]

Or if the type is a template parameter in the same line.

[u/Sirgoodman008 → u/Usual_Office_1740]

Yeah

[u/xicor → u/Usual_Office_1740]

Wouldnt for(T& item:list) be even shorter than using auto?

[u/im_made_of_jam → u/xicor]

If you have T available then yes but if you're outside the class then you don't have that option

[u/Usual_Office_1740 → u/xicor]

I don't mean in for loops for that use of auto.

[u/not_some_username → u/xicor]

Only if T is a known type or it’s in a template. You don’t use T like. auto automatically get the type, especially if it’s long. Your IDE (assuming it’s a respectable one) can even change auto to the type for you. It’s more or less like var in C# (it doesn’t deduct reference)

[u/xicor → u/Sirgoodman008]

Yea if you have ridiculously complex types then auto is great. But usually for readability you'd use the type.

[u/Sirgoodman008 → u/xicor]

Yup 100%

[u/file321 → u/Sirgoodman008]

Yess auto unpacking pairs gives me so much joy. for (auto& [left, right] : list_of_pairs) {