I've never felt that way with Python, JS, Ruby, Java, C++ or any of the other languages I've used. They are at least 10X more complex in terms of primitives and non-trivial interactions.
I love C for its warts and all, but you should treat it like a tamed wild animal.
> The current crop of C and C++ compilers will exploit undefined behaviors to generate efficient code [...], but not consistently or well. It’s time for us to take this seriously.
I assume now it's more aggressive, because undefined behavior should never be relied upon. That's the point.
The trend toward UB-based optimizations seems significant to me because they can and will take a bunch of C code which looks superficially reasonable, and which used to do X as intended, and suddenly (and perfectly legally) make it start doing Y instead. I assumed that's what barrkel was alluding to above.
And yes, I'm sure there are old optimizations which will also do that, but basic things like hoisting and reordering and unrolling and dead-code elimination don't fall into that category.
So then it's not new behavior.
And indeed, I do always use the increment operator by itself. The amount of extra thought it takes to distinguish
while(i--)
from while(--i)
just isn't worth it, when instead I could write for(;i>0;i--)
which is very clear about what the last value of i in the loop is.Actually there are a few other languages that are great for debugging runtime code behavior; Lua comes to mind.