Skip to content
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.

Sign up for GitHub

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

Jump to bottom

P2416 Inconsistent wording in the requirements for expressions #5233

Closed
frederick-vs-ja opened this issue Jan 24, 2022 · 2 comments
Closed

P2416 Inconsistent wording in the requirements for expressions #5233

frederick-vs-ja opened this issue Jan 24, 2022 · 2 comments

Comments

@frederick-vs-ja
Copy link
Contributor

As LWG has approved P2416, I think some issues may be reported here.

Currently there are two inconsistent styles used in "Result:" when presenting requirements for expressions:

  • an lvalue of type T/a prvalue of type T, and
  • T&/T,

where T is an object type in either case.
IMO we should only use one style to present the requirements for expressions, because a simple T might be ambiguous. Persumably a simple T is requiring that the expression is a prvalue of T.

Some requirements are specified by the undefined element "Return type:" (see also LWG2819) in P2416R1. I think they should be specified by "Result:".
@jensmaurer
Copy link
Member

Both have been noticed by LWG and are fixed in the latest revision.
d2416r2.pdf

@frederick-vs-ja
Copy link
Contributor Author

Oh... currently the undefined element "Value:" is used in the latest revision. Perhaps it should be replaced with "Returns:".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@frederick-vs-ja @jensmaurer