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
Core N3652, Relaxing constraints on constexpr functions #104
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
functions here, just like in C++11.
Pulled in (without the "editorial changes" - issues created for those) into motions-2013-04. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The term "address constant expression" was removed but is still used in one place in clause 14; this has been reported on -core with a suggested fix, but the fix seems too large to apply editorially.
This paper interacts with core issue 1358's wording changes; I've left comments for how those interactions are resolved by this paper.
This paper uses a new "C++ 2011" macro. I wasn't sure what naming convention produces the name \CppIII for "C++ 2003", so I called the new macro \CppFIXME for now. Should it be \CppIV?
Two editorial changes here:
-- one inserted instance of "void" is replaced by "cv void" in 3.9/10
-- one instance of "constexpr function" is replaced by "constexpr non-static member function" in 7.1.5/8