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.

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

Merged
merged 27 commits into from Nov 21, 2019

Conversation

burblebee
Copy link
Contributor

@burblebee burblebee commented Nov 16, 2019

Fixes #3404.

Issues:

  • From LWG3149:
    ** "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}."
  • LWG3272 adds this wording to [time.parse]/p1:
    "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

source/iterators.tex Outdated Show resolved Hide resolved
source/time.tex Outdated Show resolved Hide resolved
source/time.tex Outdated Show resolved Hide resolved
source/utilities.tex Show resolved Hide resolved
@jensmaurer jensmaurer added this to the post-2019-11 milestone Nov 16, 2019
@CaseyCarter
Copy link
Contributor

From LWG3149:

  • "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".

This is CWG 1844.

  • 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}."

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 std::default_constructible<S> is evaluated where S's default constructor is accessible.

@jensmaurer jensmaurer added the changes requested Changes to the wording or approach have been requested and not yet applied. label Nov 19, 2019
@jensmaurer
Copy link
Member

jensmaurer commented Nov 19, 2019

The individual commits need "Also fixes NB ..." cross-reference to the NB comments they address, where applicable.
For example, LWG 3277 fixes US 261.

@zygoloid zygoloid force-pushed the motions-2019-11-lwg-1 branch 2 times, most recently from c4ecdaa to cd4c650 Compare November 20, 2019 23:46
@zygoloid zygoloid merged commit c9d052d into master Nov 21, 2019
@zygoloid zygoloid removed the changes requested Changes to the wording or approach have been requested and not yet applied. label Nov 21, 2019
@jensmaurer jensmaurer deleted the motions-2019-11-lwg-1 branch February 18, 2020 20:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
6 participants