[axilmar]

> There is of course a reason which is well documented in the papers. Constructors, and initialization expressions can have side effects in C++. An invariant of the language is that member constructors are always invoked in declaration order, so if you were to swap the initializers around, the compiler would still have to initialize them in the original order, which would be surprising.

The following:

    Point2D pt = {.y = 5, .x = 6};

should not have meant that 'y' is initialized before 'x'. It's only a lexical convenience that exists before parsing. When the code is parsed into an AST, the actual AST would reflect the following code:

    Point2D pt = {.x = 6, .y = 5};

There is absolutely no reason to enforce declaration order.