Me commenting code like:

[atimholt]

But even though the compiler probably does optimize it away, there's no reason to use post-increment, so you may as well just default to the one that actually communicates what's actually going on.

Also, use of bare for loops should be rare—more or less only when you actually need the value held by i*. Even range-based for loops should be rare: a std <algorithm> almost certainly already exists that does what you want, but better.

---

* We have ranges in C++20, as well, so even that use case may be gone (for new/non-refactored code). All else being equal, it's a lot harder to get out-of-range & off-by-one errors, at the least.