New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[format.parse.ctx] Paragraph 14 is hard to read #6801
Comments
Call expressions where one of the following conditions is true are not core constant expressions ([expr.const]):
|
|
|
Yeah thanks, it took me a while. It's pretty late here and the run-on sentence just really messed with my head.
I've read P2757R3 and it sort of makes sense, but it's quite the surprising function and I feel like this deserves a note which explains the intent at least.
I would have much preferred the wording "Invocations of this functions" over "Call expressions". It wasn't obvious to me that the very general statement about expressions is meant to apply to calls to this particular function. Maybe that's just me, but it stumped me. I can't think of having seen "Call expressions" used in such a way anywhere else in the standard either. |
What do you think about the following wording?
The old wording was unnecessarily complex in terms of grammar. This grammatical sandwiched wasn't reader-friendly and I'm sure I'm not the last person to be stumped by it. Furthermore, the negation was counter-productive. It defined that it's "note a constant expression if the type is not one of ...". Such double negations are confusing to the reader and it is much easier to express when a call is a constant expression. I guess a note would also be nice, along the lines of:
|
The meaning of [format.parse.ctx] p14 is completely lost on me:
Ts...
are not ..." ? This isn't valid English.expressions
and I've just missed someexpressions
definition? Does it mean that calling this function is a call expression?Granted, I know very little about the formatting library but this wording just looks like gibberish to me.
The text was updated successfully, but these errors were encountered: