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

7.1.5/3 and /4 define 'constraints' that are later referred to as 'requirements' #390

Closed
zygoloid opened this issue Nov 5, 2014 · 2 comments
Closed

7.1.5/3 and /4 define 'constraints' that are later referred to as 'requirements' #390

zygoloid opened this issue Nov 5, 2014 · 2 comments

Comments

@zygoloid
Copy link
Member

zygoloid commented Nov 5, 2014

Suggestion from CWG is to change /3 and /4 to define "the requirements for a constexpr function/constructor"

Something like:

"The requirements for a constexpr function are: [...] The program is ill-formed if a constexpr function does not satisfy the requirements of a constexpr function."
@zygoloid
Copy link
Member Author

zygoloid commented Nov 5, 2014

"[...] A constexpr function is ill-formed if it does not satisfy these requirements."

@jensmaurer
Copy link
Member

This is already addressed in the current text. We say "shall satisfy the following requirements".

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
@zygoloid @jensmaurer