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
Motions 2019 11 lwg 1: P1917R0 C++ Standard Library Issues to be moved in Belfast #3472
Conversation
This is CWG 1844.
This is library-speak for "metaprogramming machinery cannot access protected or private class members regardless of the context in which they are evaluated". For example, this program: class S {
S() {}
static void f() {
S s; // Fine
static_assert(std::default_constructible<S>); // ill-formed
}
}; is ill-formed despite that |
The individual commits need "Also fixes NB ..." cross-reference to the NB comments they address, where applicable. |
…ame can also be a root-name [fs.path.gen]/p4 Use a bulleted list for conditions.
c4ecdaa
to
cd4c650
Compare
…ialization of tp_
…ormat_arg? [format.arg] Updated the reference for "Formatter requirements" to [formatter.requirements]
Also fixes NB GB 166 (C++20 CD).
…rom view_interface Also fixes NB US 297 (C++20 CD).
…ementable Also fixes NB US 261 (C++20 CD).
472529b
to
81f49eb
Compare
Fixes #3404.
Issues:
** "immediate context" is used but never defined. It is used in reference to variables, expressions, and stand-alone as ``immediate context'', yet there is only a definition for "immediate function context".
** What is an unrelated context? E.g. LWG3149 adds this in [concept.defaultconstructible]:
"Access checking is performed as if in a context unrelated to \tcode{T}."
"In the following paragraphs, let is denote an object of type basic_istream<charT, traits>, where charT and traits are template parameters in that context.".
What context?
Fixes cplusplus/nbballot#164
Fixes cplusplus/nbballot#257
Fixes cplusplus/nbballot#293