ISO/IEC JTC 1/SC 22/WG 21 P2081R0
Audience: LEWG, LWGThomas Köppe <email@example.com>
The Library Fundamentals v3 TS should be based on C++20.
The working draft of the Extensions for Library Fundamentals, Version 3 Technical Specification (“LFTSv3” or just “LFTS” for short) is currently (as of P0996R1) based on the published C++ standard, i.e. C++17. It is very unlikely, and indeed not planned at this point, that we will publish the TS before the C++20 DIS has been published (which we expect to happen at the next meeting as of the time of writing, which is Prague 2020). Therefore, we have the option of basing the TS on the C++20 DIS, and we should do this to allow us to remove facilities that have been merged into the main standard, and to take advantage of new language facilities.
If the C++20 IS is published before we complete the PDTS ballot for the LFTS, we should update the LFTS working draft to refer to the IS instead of the DIS. The acceptance of this proposal should include approval of such a future change, which would then be an editorial matter to align the wording with the design intent.
Modify [1.2, general.references] paragraphs 1, 2, and 3 as follows:
1.2 Normative references [general.references]
1. The following referenced document is indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.
14882:2017 is herein
called the C++ Standard. References to clauses within the C++
Standard are written as " C++17 §3.2". The
library described in ISO/IEC 14882:2017 clauses
20–33 is herein
called the C++ Standard Library.
3. Unless otherwise specified, the whole of the C++ Standard's Library
C++17 §20) is included into
this Technical Specification by reference.
Modify [1.3, general.namespaces] paragraphs 2:
2. Each header described in this technical specification shall import the
std::experimental as if by
Delete subclause [6.1, container.erasure].
6.1 Uniform container erasure [container.erasure] 6.1.1 Header synopsis [container.erasure.syn] 1. For brevity, […] […] are intentionally not provided. – end note]
Delete clause [11, reflection].
11 Reflection library [reflection] […]
Delete from Table 1 — C++ library headers:
Delete from Table 2 — Significant features in this technical specification:
|N4388||A Proposal to Add a Const-Propagating Wrapper to the Standard Library||[…]|
Editorially apply the new compact inline namespace syntax wherever it applies.
<experimental/utility> synopsis [utility.syn]
[Further edits not shown.]
Update section numbers, and update the “C++17-concept” names everywhere
and replace “satisfies” with “meets”, e.g. “satisfies
the requirements of
CopyConstructible” becomes “meets
the C++17CopyConstructible requirements”.
20.7.7 uses_allocator [allocator.uses] 220.127.116.11 uses_allocator trait [allocator.uses.trait]
template <class T, class Alloc> struct uses_allocator;
1. Remarks: Automatically detects whether
T has a nested
allocator_type that is convertible from
requirements ( C++17 §23.15.1).
The implementation shall provide a definition […]
[Further edits not shown.]
Update C++17-style Requires/Remarks/Postconditions into Mandates/Expects/Constraints/Ensures.
18.104.22.168 propagate_const constructors [propagate_const.ctor]
[Note: The following constructors are conditionally specified as explicit. This is typically implemented by declaring two such constructors, of which at most one participates in overload resolution. — end note]
template <class U> see below constexpr propagate_const(propagate_const<U>&& pu);
This constructor shall not participate in overload resolution unless
The constructor is specified as explicit if and only if
t_ as if direct-non-list-initializing an object of type
T with the expression
[Further edits not shown, will be included in a future revision.]