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
[C++17 DIS comment 002] update [intro.defs] to use text that can be substituted for the use of the term #1714
Comments
First pass at tackling this is here: https://github.com/cplusplus/draft/compare/master...zygoloid:iso-2?expand=1 I've split this into a multiple changes for easier review, and because I think we may want to adopt only some of them. Specifically, I would propose taking 886b293 and d9b5f40 for C++17, but not a38a131. Thoughts? |
Both changes look very nice! |
886b293 just highlights some of our more dodgy definitions, e.g. "argument of throw expression" (it's probably an operand these days that throw-expression is a first-class expression in clause 8 [expr]). |
@jwakely regarding the "on the same subject note": I agree. Further, maybe we should review clause 3 afresh: It's not clear to me which definitions should go there as opposed to being inline. Something like "access", which is essentially only used in the memory model subsection, is in Clause 3, but other more global definitions aren't, it seems. |
I've been contemplating whether to suggest we start to issue the standard in two parts (language and library). If we do that, each part gets to have its own "Terms and Definitions". Seems like something to talk over with at least Herb before making changes to the Terms and Definitions in Clause 20. |
@zygoloid: We do have interdependencies between language and library; in particular the language refers to the library for some of its semantics (cf. |
First two commits pushed to c++17, all three pushed to master. Resolution: ACCEPTED |
Per ISO directives, definitions should be drafted to replace the term in context. We need to survey the existing definitions and rephrase to suit this requirement.
The text was updated successfully, but these errors were encountered: