[expr.call] There are no expressions in an expression-list

[Endilll]

Consider [expr.call]/7:

The postfix-expression is sequenced before each expression in the expression-list and any default argument. [. . .]

The problem is that expression-list is defined as initializer-list, which contains initializer-clauses and not expressions. Maybe we should consider retiring expression-list as a grammar non-terminal to avoid confusion. It's been defined in terms of initializer-list since C++11.

Proposed resolution

Change [expr.call] paragraph 7 as follows:

The postfix-expression is sequenced before each expressioninitializer-clause in the expression-list and any default argument.

Alternatively, we can use regular font for "expression", like we do in many other places in the wording when expression-list is discussed.

[jensmaurer]

"sequenced before" applies to expressions (and maybe statements), I wouldn't want to create a precedent that it applies to "initializer-clauses" or other grammar things.

I think just doing regular-font "expression" is good enough here.

[Endilll]

I wouldn't want to create a precedent that it applies to "initializer-clauses" or other grammar things.

If that's the direction, the quoted sentence needs more changes, because it also says that grammar non-terminal postfix-expression is "sequenced before".

[Endilll]

For the reference, I found what we currently have in the wording when initializer-clauses need to be sequenced. Per [dcl.init.list]/4:

Within the initializer-list of a braced-init-list, the initializer-clauses, including any that result from pack expansions ([temp.variadic]), are evaluated in the order in which they appear. That is, every value computation and side effect associated with a given initializer-clause is sequenced before every value computation and side effect associated with any initializer-clause that follows it in the comma-separated list of the initializer-list.