This would still be a lot better for 99% of real world use cases than requiring the programmer to manually place the items in declaration order.
f(a++, b++)
That footgun doesn't seem to have very much impact in the real world that I've seen. Largely because people do not write complex expressions like that anymore. Since we already mostly avoid such expressions, we may as well take the benefit for designated initializers.It is a much smaller footgun though and I don't recall ever being bitten by it. I have definitely been bitten by member initialisation order though multiple times. Generally because of questionable designs where one member is passed as a parameter of another member and it hasn't actually been initialised yet.
Really I think the answer is to initialise in the order that initialisation is written (this is what Rust does) rather than declaration order. But that would be a breaking change so I guess they opted for the conservative choice.
On the other hand evaluation order of aggregate initializers is well defined (left to right) and there was little appetite to weaken it.
It might still happen in the future of course.
The problem is, someone thought this was a good idea, but the act of supporting it ruled out a lot of more-useful future improvements.