Applying the increment or decrement operators over the same variable more than once on the same line should be a compile-time error.
Anyway, yes, this one example has an obvious order it should be applied. But still, something like it shouldn't be allowed.
Honestly, having increment in expressions rather than a statement feels like more of a footgun than a benefit. Expressions shouldn't mutate things.
> Applying the increment or decrement operators over the same variable more than once on the same line should be a compile-time error
That would be nice, but don't forget the more general case of pointers and aliasing:
The compiler cannot statically catch every possible instance of a statement where a variable is updated more than once.