Boost-Commit :

Date view	Thread view	Subject view	Author view

Subject: [Boost-commit] svn:boost r51564 - sandbox/committee/LWG
From: bdawes_at_[hidden]
Date: 2009-03-03 08:31:24

Next message: bdawes_at_[hidden]: "[Boost-commit] svn:boost r51565 - sandbox/committee/LWG"
Previous message: bdawes_at_[hidden]: "[Boost-commit] svn:boost r51563 - sandbox/committee/LWG"

Author: bemandawes
Date: 2009-03-03 08:31:22 EST (Tue, 03 Mar 2009)
New Revision: 51564
URL: http://svn.boost.org/trac/boost/changeset/51564

Log:
cleanup
Text files modified:
sandbox/committee/LWG/0xCD1_Comments.html | 7252 ++++++++++++++++++++-------------------
1 files changed, 3649 insertions(+), 3603 deletions(-)

Modified: sandbox/committee/LWG/0xCD1_Comments.html
==============================================================================
--- sandbox/committee/LWG/0xCD1_Comments.html (original)
+++ sandbox/committee/LWG/0xCD1_Comments.html 2009-03-03 08:31:22 EST (Tue, 03 Mar 2009)
@@ -19,10 +19,10 @@
</style>

<table border="1" bordercolor="#000000" cellpadding="7"
- cellspacing="0" style="border-collapse: collapse">
+ cellspacing="0" style="border-collapse: collapse" width="1627">

 <tr valign="top">
- <td>
+ <td width="29">
 MB 

 <td>
@@ -30,18 +30,18 @@
 Subclause No./ 
 Annex (e.g. 3.1)

- <td>
+ <td width="107">
 Para/ 
- Figure/ Table/ Note<td>
+ Figure/ Table/ Note<td width="38">
 Type 

- <td>
+ <td width="510">
 Comment (justification for change) by the MB

- <td>
+ <td width="535">
 Proposed change by the MB

- <td>
+ <td width="89">
 
 Disposition
@@ -49,19 +49,19 @@
 

 <tr valign="top">
- <td>
+ <td width="29">
 FR 1

 <td>
 General Comment

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 ge

- <td>
+ <td width="510">
 Interactions between several
 new features appear obscure, and very few examples are
 offered to guide understanding of the formal text on
@@ -70,26 +70,26 @@
 We worry about the complexity
 of the programming model so created.

- <td>
+ <td width="535">
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 1

 <td>
 1-16

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 ge/te

- <td>
+ <td width="510">
 The
 active issues identified in WG21 N2803, C++ Standard Core
 Language Active Issues, must be addressed and appropriate
@@ -103,7 +103,7 @@
 "http://www.open-std.org/jtc1/sc22/wg21/docs/cwg_active.html">
 http://www.open-std.org/jtc1/sc22/wg21/docs/cwg_active.html>

- <td>
+ <td width="535">
 
 Appropriate action would include making changes to the CD,
 identifying an issue as not requiring a change to the CD,
@@ -111,47 +111,47 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 CA-1

 <td>
 

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Ge

- <td>
+ <td width="510">
 There are quite a number of defects for the current CD
 recorded in SC22/WG21-N2803 and N2806

- <td>
+ <td width="535">
 Consider these comments and update ISO/IEC CD 14882
 accordingly

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 DE-1

 <td>
 1 through 16

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 ge/te

- <td>
+ <td width="510">
 DE-1 Consider addressing a significant part of the
 unresolved core language issues presented in WG21 document
 N2791 "C++ Standard Core Language Active Issues, Revision
@@ -159,192 +159,192 @@
 http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2008/n2791.html
 .

- <td>
+ <td width="535">
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 CH 2

 <td>
 all

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 The issues on the issues lists shall be addressed before
 the standard becomes final.

- <td>
+ <td width="535">
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 3

 <td>
 all

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 Latin abbreviations are presented incorrectly.

- <td>
+ <td width="535">
 Italicize all
 Latin abbreviations, append commas after each occurrence of
 i.e. and e.g., and remove extraneous space
 after each such abbreviation.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 FR 3

 <td>
 1 [intro.scope]

- <td>
+ <td width="107">
 2

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 C++ is split at the end of line.

- <td>
-  <td>
+ <td width="535">
+  <td width="89">
  <tr valign="top">
- <td>
+ <td width="29">
 US 4

 <td>
 1.1

- <td>
+ <td width="107">
 2

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 There is a bad line break in
 "C++".

- <td>
-  <td>
+ <td width="535">
+  <td width="89">
  <tr valign="top">
- <td>
+ <td width="29">
 UK 1

 <td>
 1.1

- <td>
+ <td width="107">
 2

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 List of additional facilities over C has
 been extended with this standard, so should be mentioned in
 the introductory material.

- <td>
+ <td width="535">
 Add the following to the list in 1.1p2:
 atomic operations concurrency alignment control
 user-defined literals attributes

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 FR 4

 <td>
 1.2 [intro.refs]

- <td>
+ <td width="107">
 1

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 Is the lack of reference to ISO/CEI 9899/AC3:2007
 voluntary?

- <td>
+ <td width="535">
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 2

 <td>
 1.2

- <td>
+ <td width="107">
 1

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 
 We recommend taking the latest update to
 each listed standard, yet the C standard is quite
 deliberately held back to the 1990 version without
 comment.+

- <td>
+ <td width="535">
 ... not sure ...

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 3

 <td>
 1.3.1

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 The definition of an argument does not seem
 to cover many assumed use cases, and we believe that is not
 intentional.

- <td>
+ <td width="535">
 Revise the
 definition of argument to answer question such as: Are
 lambda-captures arguments? Are type names in a throw-spec
@@ -359,145 +359,148 @@
 instantiations? What about user-defined literals where
 parens are not used?

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 4

 <td>
 1.3.3

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 This definition is essentially worthless,
 as it says nothing about what distinguished a diagnostic
 message from other output messages provided by the
 implementation

- <td>
+ <td width="535">
 ... add
 something about the diagnostic message being a message
 issues by the implementation when translating a program
 that violates the rules of the standard. ...

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 FR 5

 <td>
- 1.3.4 [defns.dynamic.type]
+ 1.3.4 
+ [defns.dynamic.type]

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 "The dynamic type of an rvalue expression is its static
 type." Is this true with rvalue references?

- <td>
+ <td width="535">
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 5

 <td>
 1.3.5

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 The wording is unclear as to whether it is the input or
 the implementation "that is not a well-formed program".

- <td>
+ <td width="535">
 Reword to clarify that it is the input that is here
 considered not well-formed.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 FR 6

 <td>
- 1.3.6 [defns.impl.defined]
+ 1.3.6 
+ [defns.impl.defined]

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 There is a page break between the title and the
 paragraph.

- <td>
+ <td width="535">
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 FR 7

 <td>
- 1.3.13 [defns.undefined]
+ 1.3.13 
+ [defns.undefined]

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 [intro.execution]/5 explicitly allows non causal
 undefined behaviour,

- <td>
+ <td width="535">
 Adding it to the note outlying possible undefined
 behaviours.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 6

 <td>
 1.3.14

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 ge

- <td>
+ <td width="510">
 
 Unspecified behavior does not clearly state whether or not
 undefined behavior is permitted. (The standard says that
@@ -505,350 +508,351 @@
 but what happens if the range is not delineated? Is a
 crash, or worse, allowed?) 

- <td>
+ <td width="535">
 Clearly state whether or not
 Unspecified behavior includes undefined behavior.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 FR 8

 <td>
- 1.4 [intro.compliance]
+ 1.4 
+ [intro.compliance]

- <td>
+ <td width="107">
 8

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 The paragraph as its stands seems to require that
 violations of the ODR (which make a program ill-formed) are
 required to be diagnosed if the program also uses an
 extension which defines some cases of ODR.

- <td>
+ <td width="535">
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 5

 <td>
 1.5

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Ge

- <td>
+ <td width="510">
 Missing checklist of implementation defined
 behaviour (see ISO/IEC TR 10176, 4.1.1p6)

- <td>
+ <td width="535">
 Provide a new annex with the missing
 checklist

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 6

 <td>
 1.5

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Ge

- <td>
+ <td width="510">
 Missing annex describing potential
 incompatibility to previous edition of the standard (see
 ISO/IEC TR 10176, 4.1.1p9)

- <td>
+ <td width="535">
 Provide a new annex with the missing
 documentation. See n2733(08-0243) for a starting point

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 7

 <td>
 1.5

- <td>
+ <td width="107">
 2

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 There is no mention of Clause 17.

- <td>
+ <td width="535">
 Include Clause 17 among the list of Clauses that specify
 the Standard Library.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 8

 <td>
 1.5

- <td>
+ <td width="107">
 2

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 The paragraph
 omits to mention concepts and concept maps among its list
 of entities defined in the Standard Library. 

- <td>
+ <td width="535">
 Mention concepts and concept maps among the list of
 entities.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 9

 <td>
 1.6

- <td>
+ <td width="107">
 1

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 The
 syntax description does not account for lines that wrap. 

- <td>
+ <td width="535">
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 10

 <td>
 1.7

- <td>
+ <td width="107">
 3

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 The term thread is used before
 defined.

- <td>
+ <td width="535">
 Reference 1.10 [intro.multithread].

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 11

 <td>
 1.7

- <td>
+ <td width="107">
 ¶ 3 last sent.

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 The phrase “threads of execution” should be
 accompanied by a reference to [intro.multithread].

- <td>
+ <td width="535">
 Insert the recommended reference.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 12

 <td>
 1.7

- <td>
+ <td width="107">
 ¶ 3 first sent.

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 A memory location is not an object as the sentence
 claims.

- <td>
+ <td width="535">
 Clarify that a memory location “holds” an
 object rather than that it “is” an object.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 13

 <td>
 1.7

- <td>
+ <td width="107">
 ¶ 3 last sent.

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 It is unclear what is meant by memory locations that are
 "separate": are they distinct? non-overlapping? how much
 "separation" is needed?

- <td>
+ <td width="535">
 Provide either a better definition of
 “separate” or reword (this and subsequent
 paragraphs) to avoid this term.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 14

 <td>
 1.7

- <td>
+ <td width="107">
 ¶ 4

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 The phrase "no matter what the sizes of the intervening
 bit-fields happen to be" contradicts the claim of
 separation "by a zero-length bit-field declaration".

- <td>
+ <td width="535">
 Delete the “no matter…” phrase, or
 resolve the contradiction in a different way.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 15

 <td>
 1.7

- <td>
+ <td width="107">
 ¶ 5

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 A struct does not “contain” memory
 locations.

- <td>
+ <td width="535">
 Reword so that a struct is “held in” one or
 more memory locations.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 16

 <td>
 1.9

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 

- <td>
+ <td width="510">
 The discussion of observable behavior in 1.9 is not
 consistent with the addition of threads to the language.
 Volatile reads and writes and other observable actions no
 longer occur in a single "sequence”.

- <td>
+ <td width="535">
 Remove/replace various occurrences of "sequence" in 1.9.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 8

 <td>
 1.9

- <td>
+ <td width="107">
 5

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 With parallel execution there is no longer
 the idea of a single execution sequence for a program.
 Instead, a program may be considered a set of exectution
 sequences.

- <td>
+ <td width="535">
 Update first sentance as: A conforming
 implementation executing a well-formed program shall
 produce the same observable behavior as one of the possible
@@ -856,23 +860,23 @@
 of the abstract machine CONFORMING TO THE MEMORY MODEL
 (1.10) with the same program and the same input.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 7

 <td>
 1.9

- <td>
+ <td width="107">
 6

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 Does the term 'sequence' imply all
 reads/writes through volatile memory much be serialized,
 and cannot occur in parallel on truly parallel hardware?
@@ -881,56 +885,56 @@
 multiple sequences are constrained by the memory model and
 happens-before relationships defined in 1.10

- <td>
+ <td width="535">
 Replace 'sequence' with 'sequences'.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 FR 9

 <td>
 1.9 [intro.execution]

- <td>
+ <td width="107">
 16

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 This example use int *v while the other examples seems
 to use notation like int* v.

- <td>
+ <td width="535">
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 17

 <td>
 1.10

- <td>
+ <td width="107">
 1

- <td>
+ <td width="38">
 Ge

- <td>
+ <td width="510">
 This definition of
 “thread” is poor, and assumes the user already
 knows what multi-threaded means (probably true!). In
 particular, it does not deal adequately with the concept
 that all threads share the same address space.

- <td>
+ <td width="535">
 Replace first
 sentence of para 1 as follows:
@@ -947,30 +951,30 @@
 functions, and automatic variables, are accessible to all
 threads in the same program.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 9

 <td>
 2.1

- <td>
+ <td width="107">
 2, 4

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 Undefined behaviour is a drastic way to
 silently ignore minor issues. The cases in this paragraph
 could be easily defined. In this case opt for conditionally
 supported behaviour, which mandates a diagnostic if the
 compiler is not prepared to handle the syntax consistently.

- <td>
+ <td width="535">
 Replace
 undefined behaviour with conditionally supported behavior.
 Conditional behaviour may be implementation defined,
@@ -981,51 +985,53 @@
 implictly added, with an empty line to follow if the last
 character was a back-slash.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 10

 <td>
 2.1

- <td>
+ <td width="107">
 3

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 Implementation
 defined seems unnecessarily burdensome for negligible gain.
 I am yet to see code that depended on whether non-empty
 sequences of whitespace were concatenated. Better left
 unspecified.

- <td>
+ <td width="535">
 How the compiler treats non-empty sequences
 of whitespace should be left unspecified, rather than
 implementation-defined.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 FR 10

 <td>
- 2.1 [lex.phases]/5 and 2.2 [lex.charset]/3
+ 2.1 [lex.phases]/5 
+ and 
+ 2.2 [lex.charset]/3

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 [defns.multibyte] "the
 extended character set."

@@ -1052,14 +1058,14 @@
 different locale. During phase 5, they are using an
 implementation defined char set.

- <td>
+ <td width="535">
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK

@@ -1068,28 +1074,28 @@
 <td>
 2.3

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 Trigraphs are a complicated solution to an
 old problem, that cause more problems than they solve in
 the modern environment. Unexpected trigraphs in string
 literals and occasionally in comments can be very confusing
 for the non-expert.

- <td>
+ <td width="535">
 Deprecate the whole of 2.3 and move it to
 appendix D.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK

@@ -1098,13 +1104,13 @@
 <td>
 2.4, 2.8

- <td>
+ <td width="107">
 2

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 This undefined
 behaviour in token concatenation is worrying and we believe
 hard to justify. An implementation should either support
@@ -1113,106 +1119,107 @@
 implementations, although unconditionally requiring a
 diagnostic would lead to more portable programs.

- <td>
+ <td width="535">
 Replace undefined behaviour with
 conditionally supported behaviour with implementation
 defined semantics.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 18

 <td>
 2.4

- <td>
+ <td width="107">
 ¶ 2

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 The paragraph begins with an empty line.

- <td>
+ <td width="535">
 Delete the empty line.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 FR 11

 <td>
 2.4 [lex.pptokens]

- <td>
+ <td width="107">
 3

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 There are spurious empty lines.

- <td>
+ <td width="535">
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 FR 12

 <td>
- 2.5 [lex.digraph] and 2.11 [lex.key]/2
+ 2.5 [lex.digraph] 
+ and 2.11 [lex.key]/2

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 The alternative representations are reserved as such
 even in attribute. Is that what is wanted?

- <td>
+ <td width="535">
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 FI 2

 <td>
 2.5

- <td>
+ <td width="107">
 Table 2

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 Add eq, for spelling out == in order to distinguish it
 from the assignment operator.

- <td>
+ <td width="535">
 See eq-keyword.doc, eq-keyword.ppt

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK

@@ -1221,27 +1228,27 @@
 <td>
 2.9

- <td>
+ <td width="107">
 2

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 This text is confusing in isolation, as it
 implies pp-numbers do not have a value in translation phase
 4 when evaluating #if preprocessor expressions.

- <td>
+ <td width="535">
 Add a note with a cross-refernce to 16.1
 that a pp-number may briefly acquire a value during
 translation phase 4 while evaluating #if expressions.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK

@@ -1250,104 +1257,103 @@
 <td>
 2.11

- <td>
+ <td width="107">
 table 3

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 The table is
 nearly sorted, but not quite. It was sorted in previous
 versions of the standard.

- <td>
+ <td width="535">
 Sort the table.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 1

 <td>
 2.11

- <td>
+ <td width="107">
 Table 3

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 Keywords in the table are listed disorderly. Also, a
 part of a frame of the table is not drawn.

- <td>
+ <td width="535">
 Sort it in alphabetical order.
 Complete the table frame.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 19

 <td>
 2.13.1

- <td>
+ <td width="107">
 Table 5, rows “l or L” and “ll or
 LL”

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 The final entry in the last column (“unsigned long
 int”) is incorrect.

- <td>
+ <td width="535">
 Replace the incorrect entries by “unsigned long
 long int”.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 20

 <td>
 2.13.1, 2.13.3

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 Long strings of digits in
 literals are a continuing problem in the production and
 maintenance of programs.

- <td>
+ <td width="535">
 
 Adopt the 1983 technology of Ada and use underscores to
- separate digits. <a href=
+ separate digits. <a href=
 "http://www.google.com/url?sa=D&q=http%3A%2F%2Fwww.open-std.org%2FJTC1%2FSC22%2FWG21%2Fdocs%2Fpapers%2F2007%2Fn2281.html"
 target=
- "_blank">http://www.open-std.org/JTC1/SC22/WG21/docs/papers/2007/n2281.html>
+ "_blank">http://www.open-std.org/JTC1/SC22/WG21/docs/papers/2007/n2281.html>

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK

@@ -1356,28 +1362,28 @@
 <td>
 2.13.2

- <td>
+ <td width="107">
 2

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 Inconsistency between definition of a
 multicharacter literal and a wide character literal
 containing multiple c-chars.

- <td>
+ <td width="535">
 Define the term
 multicharacter wide literal for a wchar_t literal
 containing multiple elements, and specify its type is
 integer (or wider)

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK

@@ -1386,64 +1392,64 @@
 <td>
 2.13.2

- <td>
+ <td width="107">
 3

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 Not immediately clear why the question mark
 needs escaping. A note would help.

- <td>
+ <td width="535">
 Add a note
 explaining that the ? character may need escaping to avoid
- accidentally creating a trigraph.<td>
+ accidentally creating a trigraph.<td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 2

 <td>
 2.13.4

- <td>
+ <td width="107">
 
 1st para, 2nd line

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 Typo, R"..." should be
 R"[...]"

- <td>
+ <td width="535">
 Correct typo.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 3

 <td>
 2.13.4

- <td>
+ <td width="107">
 2nd para<td>
+ style="font-size: 11pt">para<td width="38">
 te

- <td>
+ <td width="510">
 We think that the explanation of d-char-sequence is not
 enough.

- <td>
+ <td width="535">
 Add
 the following.

@@ -1502,25 +1508,25 @@
 - end note]

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 4

 <td>
 2.13.4

- <td>
+ <td width="107">
 3rd para, 1st line of
 example

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 
 Typo. Lack of a necessary backslash in the first line of
 the example as follows:
@@ -1552,110 +1558,110 @@

 c]";

- <td>
+ <td width="535">
 Correct typo.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 21

 <td>
 2.13.4

- <td>
+ <td width="107">
 ¶ 3

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 The paragraph, marked as a Note, contains an embedded
 example not marked as such.

- <td>
+ <td width="535">
 Denote the code (and perhaps also its commentary) as an
 Example.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 22

 <td>
 2.13.4

- <td>
+ <td width="107">
 ¶ 3

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 The code does not have the effect predicted by its
 accompanying narrative.

- <td>
+ <td width="535">
 Append a backslash to the first line of the code.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 5

 <td>
 2.13.4

- <td>
+ <td width="107">
 
 11th para, Table 7

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 It is not explicit how to combine raw-string and
 non-raw-string.

- <td>
+ <td width="535">
 Add rules containing raw-string in the table 7.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 FR 13

 <td>
 2.13.4 [lex.string]

- <td>
+ <td width="107">
 3

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 Shouldn't the assert be

 assert(std::strcmp(p, "a\nb\nc") == 0);

- <td>
+ <td width="535">
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK

@@ -1664,13 +1670,13 @@
 <td>
 2.13.4

- <td>
+ <td width="107">
 10

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 It would be
 preferred for attempts to modify string literals to be
 diagnosable errors. This is not possible due to the
@@ -1684,16 +1690,16 @@
 covered under the const_cast rules so needs no further
 detail here.

- <td>
+ <td width="535">
 (asssuming deprecated conversion to
 non-const array is removed or can be turned off) Strike the
 sentence on undefined behaviour.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK

@@ -1702,13 +1708,13 @@
 <td>
 2.13.4

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 The addition of
 static_assert (7p4) to the language raises the need to
 concatenate string representations of integral constant
@@ -1721,7 +1727,7 @@
 required, although generalizing to other literal types
 would be useful.

- <td>
+ <td width="535">
 Define a syntax to support string-ization
 of integral constant expressions in a form eligible for
 string literal concatenation, 2.13.4p6. Suggested syntax:
@@ -1729,11 +1735,11 @@
 although it could combine with type specifier in the same
 way that the R prefix does, supporting u8I, uI, UI and LI.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK

@@ -1742,18 +1748,18 @@
 <td>
 2.13.4

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 The grammar for string literal is becoming
 unwieldy and could easily be refactored into the type
 optional specifier and the string contents.

- <td>
+ <td width="535">
 Refactor
 string-literal grammar as: (note - current Drupal view
 loses formatting which is vital to clearly read the
@@ -1762,28 +1768,28 @@
 u8 u U L string-literal-body: " s-char-sequenceOPT " R
 raw-string

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 FR 14

 <td>
 3 [basic]

- <td>
+ <td width="107">
 7

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 "In general it is necessary to determine whether a name
 denotes one of these entities before parsing the program
 that contains it."

- <td>
+ <td width="535">
 Would prefer

 "... before continuing to
@@ -1798,35 +1804,35 @@
 as some names denotes entities declared after the first
 occurrence.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 FR 15

 <td>
 3 [basic]

- <td>
+ <td width="107">
 8

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 /operator-function-id/,
 /conversion-function-id/, /template-id/ are followed by a
 space and then a "s" while usually such production names
 aren't followed by a space when put in plural (see
- /identifier/).<td>
+ /identifier/).<td width="535">
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK

@@ -1835,13 +1841,13 @@
 <td>
 3

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Ge

- <td>
+ <td width="510">
 Chapter 3
 ("Basic concepts") provides common definitions used in the
 rest of the document. Now that we have concepts as a
@@ -1849,14 +1855,14 @@
 as it does not refer to the language feature but to
 definitions used in the document.

- <td>
+ <td width="535">
 Change the title to "Basic definitions".

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK

@@ -1865,26 +1871,26 @@
 <td>
 3

- <td>
+ <td width="107">
 2

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 Concepts is now the name of a specific
 feature of the language, the term now risks confusion and
 ambiguity when used in the more general sense.

- <td>
+ <td width="535">
 Rename the chapter Basic ???. THe note in
 p2 specifically needs similar rewording

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK

@@ -1893,26 +1899,26 @@
 <td>
 3

- <td>
+ <td width="107">
 6

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 References are
 frequently considered variables, but this definition only
 applies to objects.

- <td>
+ <td width="535">
 Add "or reference" after both uses of
 "object"

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK

@@ -1921,26 +1927,26 @@
 <td>
 3.1

- <td>
+ <td width="107">
 2

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 
 alias-declarations are not definitions and should be added
 to the list

- <td>
+ <td width="535">
 Add alias-declaration after typedef
 declaration.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK

@@ -1949,13 +1955,13 @@
 <td>
 3.1

- <td>
+ <td width="107">
 2

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 The current
 words suggest the declaration of a static integral constant
 data member of a class cannot be a definition. Trying to
@@ -1963,17 +1969,17 @@
 more confusion than it solves, so suggest a footnote to
 call out the special case

- <td>
+ <td width="535">
 Add a footnote attached to the static data
 membmer rule: *static data member delcarations of intergral
 type may also be definitions if a constant integral
 expression is provided for an initializer.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK

@@ -1982,13 +1988,13 @@
 <td>
 3.1

- <td>
+ <td width="107">
 3

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 Example is
 misleading as implicitly defined default constructor uses
 default initialization, not value initialization, for
@@ -1996,17 +2002,17 @@
 makes no difference, but it makes a big difference for
 fundamental types and pointers.

- <td>
+ <td width="535">
 Remove the : s() from the illustrated
 default constructor: struct C { std::string s; C() { }
 C(const C& x): s(x.s) { } C& operator=(const C&
 x) { s = x.s; return *this; } ~C() { } };

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK

@@ -2015,26 +2021,26 @@
 <td>
 3.2

- <td>
+ <td width="107">
 1

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 THe one
 definition rule should cover references, and unless the
 term 'variable' is extended to cover references the list in
- this paragraph is incomplete.<td>
+ this paragraph is incomplete.<td width="535">
 Either include references in the definition
 of 'variable' (see earlier comment) or add reference to the
 list in this paragraph.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK

@@ -2043,50 +2049,51 @@
 <td>
 3.2

- <td>
+ <td width="107">
 4

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 A class type
 must be complete when catching exceptions, even by
 reference or pointer. See 15.3.

- <td>
+ <td width="535">
 Add "when used in an exception-handler
 (15.3)" to the list.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 FR 16

 <td>
- 3.3 [Declarative regions and scopes.]
+ 3.3 [Declarative 
+ regions and scopes.]

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 The scope of function
 parameters is defined, but what is the scope of template
 parameters?

- <td>
+ <td width="535">
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK

@@ -2095,24 +2102,24 @@
 <td>
 3.3.1

- <td>
+ <td width="107">
 3

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 Class templates
 are not classes, so we should include this case.

- <td>
+ <td width="535">
 ammend "class" to "class or class template"

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK

@@ -2121,42 +2128,43 @@
 <td>
 3.3.10

- <td>
+ <td width="107">
 3

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 operators and conversion functions do not
 have names, yet are susceptible to 'name hiding' within a
 class - indeed we rely on this for the implicitly declared
 copy-assignment operator.

- <td>
+ <td width="535">
 Add the
 additional phrase "The declaration of an operator or
 conversion function in a derived class (Clause 10) hides
 the declaration of an operator or conversion function of a
 base class of the same operator or type;"

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 FR 17

 <td>
- 3.5 [Program and linkage]
+ 3.5 [Program 
+ and linkage]

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 This section does not specify
 whether concept names have linkage.

@@ -2165,54 +2173,54 @@
 that would be a bit surprising and curious. What is the
 rationale?

- <td>
+ <td width="535">
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 30

 <td>
 3.5

- <td>
+ <td width="107">
 2

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 This paragraph implies concepts have no
 linkage (do they need it?) and that the entities behind
 names without linkage cannot be used in other scopes. This
 maybe a bigger problem for concept maps?

- <td>
+ <td width="535">
 Add a note to clarify that concepts don't
 need linkage.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 31

 <td>
 3.5

- <td>
+ <td width="107">
 4

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 What is the linkage of names declared
 inside a namespace, in turn declared inside an anonymous
 namespace? It is not clear why such a namespace has no
@@ -2220,72 +2228,73 @@
 should lose linkage with it, which we assume is the
 intended consequence.

- <td>
+ <td width="535">
 Clarify rules for namespaces inside nested
 namespaces, or remove the restriction.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 23

 <td>
 3.5

- <td>
+ <td width="107">
 6

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 Bad
 paragraph break.

- <td>
+ <td width="535">
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 FR 18

 <td>
 3.5 [basic.link]

- <td>
+ <td width="107">
 6

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 The paragraph number is not aligned with the text.

- <td>
+ <td width="535">
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 FR 19

 <td>
- 3.6 [Start and termination]
+ 3.6 [Start 
+ and termination]

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 This section completely
 ignores the real world and practical case of dynamically
 linked or loaded libraries. In current computing
@@ -2299,55 +2308,55 @@

 

- <td>
+ <td width="535">
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 32

 <td>
 3.6.1

- <td>
+ <td width="107">
 3

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 Do we really want to allow: constexpr int
 main() { return 0; } as a valid program?

- <td>
+ <td width="535">
 Add constexpr to
 the list of ill-formed things to annotate main 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 24

 <td>
 3.6.1

- <td>
+ <td width="107">
 4

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 std::quick_exit is not
 referenced.

- <td>
+ <td width="535">
 
 Reference std::quick_exit as well as std::exit in saying
 that automatic objects are not destroyed. It should
@@ -2356,48 +2365,48 @@
 from within destructors for static or thread duration
 objects.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 25

 <td>
 3.6.3

- <td>
+ <td width="107">
 ¶ 2 last sent.

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 The parenthesized phrase, introduced via
 “i.e.” is in the nature of an example.

- <td>
+ <td width="535">
 Change “i.e.” to “e.g.”

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 6

 <td>
 3.7.4.1

- <td>
+ <td width="107">
 4th para, 4th
 line

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 
 Typo.

@@ -2437,26 +2446,26 @@

 

- <td>
+ <td width="535">
 Correct typo.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 DE-3

 <td>
 3.7.4.3

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 DE-3 It is
 unclear whether the following code has well-defined
@@ -2469,31 +2478,31 @@

 delete &i;

- <td>
+ <td width="535">
 Clarify that &i is considered a safely-derived
 pointer value.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 26

 <td>
 3.8

- <td>
+ <td width="107">
 1 and 5

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 Use of object fields during
 destruction is excessively and erroneously constrained.

- <td>
+ <td width="535">
 See
 the attached document "Issues with the C++ Standard" under
 Chapter 3 "Use of objects, especially from other threads,
@@ -2501,46 +2510,46 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 27

 <td>
 3.9

- <td>
+ <td width="107">
 ¶ 9 first sent.

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 There is a superfluous/extraneous “and”.

- <td>
+ <td width="535">
 Delete “and” from the phrase “and
 std::nullptr_t”.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 FR 20

 <td>
 3.9 [Types]

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 The phrase 'effective type'
 is defined and used in a way that is incompatible with C99.
 Such a deliberate incompatible choice of terminology is
@@ -2549,32 +2558,32 @@
 strongly suggest that the phrase 'effective type' not be
 used in such an incompatible way.

- <td>
+ <td width="535">
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 7

 <td>
 3.9.2

- <td>
+ <td width="107">
 3rd para, 13th
 line

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 over-aligned type was added as new notion. So it is
 preferable to add the link after that.

- <td>
+ <td width="535">
 Add
 (3.11) after over-aligned type as the link.

@@ -2591,55 +2600,55 @@
 valid pointer value for an over-aligned type(3.11).—end note ]

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 28

 <td>
 3.9.3

- <td>
+ <td width="107">
 ¶ 5 first sent.

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 The closing
 braces of the first two sets are preceded by extraneous
 space.

- <td>
+ <td width="535">
 Delete the extra spaces.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 DE 4

 <td>
 4.2

- <td>
+ <td width="107">
 p2

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 DE-4 The deprecated conversion from string literals to
 pointer to non-const character types should be limited to
 those conversions and types of string literals that were
 already present in ISO/IEC 14882:2003, or the deprecated
 conversions should be removed entirely.

- <td>
+ <td width="535">
 Consider
 applying the proposed resolution presented in core issue
@@ -2650,28 +2659,28 @@
 "pointer to char32_t" in 4.2 paragraph 2 and 15.1 paragraph
 3.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 CH 1

 <td>
 4.9 and 5.2.9

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 With respect to the target type, pointer to members
 should behave like normal pointers (least surprise
 principle).

- <td>
+ <td width="535">
 The standard
 should allow implicit conversions from ``pointer to member
@@ -2680,157 +2689,157 @@
 of class type and B is a public base of D, It should allow
 explicit conversion the other way around.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 DE-5

 <td>
 4.11, 5.3.1, 5.5

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 DE-5 Ref-qualification has not been integrated with
 pointer-to-members.

- <td>
+ <td width="535">
 Review implicit
 conversions (4.11), forming pointer-to-members (5.3.1), and
 dereferencing pointer-to-members (5.5) for type-safety
 concerns in the presence of ref-qualifiers on the member.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 33

 <td>
 4.13

- <td>
+ <td width="107">
 1

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 We have: "No two signed integer types shall
 have the same rank ..." "the rank of char shall equal the
 rank of signed char" Can we therefore deduce that char may
 not be signed?

- <td>
+ <td width="535">
 Replace the
 first sentence with "No two signed integer types shall have
 the same rank, even if they have the same representation,
 except that signed char shall have the same rank as char
 even if char is signed (3.9.1/1)."

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 34

 <td>
 4.13

- <td>
+ <td width="107">
 1

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 6th bullet, "the
 rank of char" - first letter should be capitalised for
 consistency with the other bullets

- <td>
+ <td width="535">
 The rank of char

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 36

 <td>
 5.1

- <td>
+ <td width="107">
 1

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 Primary
 expressions are literals, names, names qualified by the
 scope resolution operator ::, and lambda expressions. The
 immediately following grammar flatly contradicts this -
- this and (e) are also lambda expressions.<td>
+ this and (e) are also lambda expressions.<td width="535">
 Delete this paragraph.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 37

 <td>
 5.1

- <td>
+ <td width="107">
 11

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 Member function
 templates are not member functions, so should also be
 listed in the 3rd bullet

- <td>
+ <td width="535">
 Add member function templates to the 3rd
 bullet

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 38

 <td>
 5.1

- <td>
+ <td width="107">
 3

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 this might be useful in a few more places
 than it is permitted, specifically in decltype expressions
 within a class. Two examples that would be ill-formed at
@@ -2838,27 +2847,27 @@
 this_type; decltype( [this]{ return this->memfun(); } )
 my_lambda;

- <td>
+ <td width="535">
 ... words to follow ...

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 8

 <td>
 5.1

- <td>
+ <td width="107">
 7th para, Syntax rules

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 In
 the current syntax definition, a scope operator(::) cannot
 be applied to decltype, but it should be. It would be
@@ -2871,7 +2880,7 @@
 decltype(v)::value_type i = 0;
 // int i = 0;

- <td>
+ <td width="535">
 Add
 “decltype ( expression ) :: “ to
 nested-name-specifier syntax like below.
@@ -2904,23 +2913,23 @@
 "text-indent: 0.13in; margin-bottom: 0in">decltype (
 expression ) ::

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 9

 <td>
 5.1.1

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 It
 would be preferable that “&&” could be
 specified in a lambda expression to declare move capture.
@@ -3094,29 +3103,29 @@

 

- <td>
+ <td width="535">
 Add
 move capture in a lambda expression.

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 10

 <td>
 5.1.1

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 In
 the current syntax definition, a returned type of a
 function object cannot be obtained by using result_of from
@@ -3152,54 +3161,54 @@
 function object without result_type. But it is preferable
 to be able to obtain it with template.

- <td>
+ <td width="535">
 Add
 result_type to the syntax of an unnamed function object
 generated by a lambda expression.

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 29

 <td>
 5.1.1

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 The
 standard does not state whether or not direct recursion of
 lambdas is possible.

- <td>
+ <td width="535">
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 30

 <td>
 5.1.1

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 
 The standard does not clarify the
 meaning of 

- <td>
+ <td width="535">
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 31

 <td>
 5.1.1

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 
 The current wording does not specify
 how context capturing and name resolution
@@ -3235,33 +3244,33 @@
 inner lambda refers to the outer lambda's locals variables
 and parameters.

- <td>
+ <td width="535">
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 45

 <td>
 5.1.1

- <td>
+ <td width="107">
 para 2

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 Lambda is a language feature with an
 apparent dependency on <functional>. This increases
 dependency of language on library, and is inconsistent with
 the definition of freestanding in 17.6.2.4.

- <td>
+ <td width="535">
 Change the text
 "a closure object behaves as a function object" to "a
 closure object is a built-in object which behaves as a
@@ -3273,11 +3282,11 @@
 on library. (Marked as technical comment anyway because
 this clarity is technically important).

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US
 32

@@ -3286,64 +3295,64 @@
 <td>
 5.1.1

- <td>
+ <td width="107">
 3

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 The
 final italic "this" in the paragraph should be a teletype
 "this".

- <td>
+ <td width="535">
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 39

 <td>
 5.1.1

- <td>
+ <td width="107">
 11

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 This paragraph lists all the special member
 functions for the class representing a lambda. But it omits
 the destructor, which is awkward.

- <td>
+ <td width="535">
 Add "F has an implicitly-declared
 destructor".

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 40

 <td>
 5.1.1

- <td>
+ <td width="107">
 12

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 If one or more
 names in the effective capture set are preceded by &,
 the effect of invoking a closure object or a copy after the
@@ -3355,30 +3364,30 @@
 behaviour: int i; reference_closure<void ()> f; if
 (blah) { f = [&i]() { }; } if (f) f();

- <td>
+ <td width="535">
 If one or more names in the effective
 capture set are preceded by &, the effect of invoking a
 closure object or a copy after the lifetime of any of the
 variables referenced has ended is undefined.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 41

 <td>
 5.1.1

- <td>
+ <td width="107">
 12

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 For argument dependant lookup (3.4.2) the
 associated namespaces for a class include its bases, and
 associated namespaces of its bases. Requiring the result of
@@ -3389,35 +3398,35 @@
 relying on the idea of implicitly slicing objects is
 uncomfortable.

- <td>
+ <td width="535">
 Replace inheritance with implicit
 conversion.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 42

 <td>
 5.1.1

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 A lambda with an empty capture list has
 identical semantics to a regular function type. By
 requiring this mapping we get an efficient lambda type with
 a known API that is also compatible with existing operating
 system and C library functions.

- <td>
+ <td width="535">
 Add a new
 paragraph: "A lambda expression with an empty capture set
 shall be convertible to pointer to function type R(P),
@@ -3428,24 +3437,24 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 43

 <td>
 5.1.1

- <td>
+ <td width="107">
 12

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 The note spells
 out the intent that objects from lambda-expressions with an
 effective capture list of references should be implemented
@@ -3456,28 +3465,28 @@

 

- <td>
+ <td width="535">
 ... provvide exceptions in the right places
 ...

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 44

 <td>
 5.1.1

- <td>
+ <td width="107">
 12

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 There is a
 strong similarity between a [&]{} lambda capturing a
 stack frame, and a [this]{} lambda binding a member
@@ -3490,29 +3499,29 @@

 

- <td>
+ <td width="535">
 Extend reference_closure requirement to
 cover [this] lambdas. Consider a simple syntax for creating
 such bound expressions.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 46

 <td>
 5.1.1

- <td>
+ <td width="107">
 para 12

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 The requirement that a lambda meeting
 appropriate conditions be an object derived from
 reference_closure makes lambda the language feature
@@ -3520,7 +3529,7 @@
 of the language on the library and bloats the definition of
 freestanding C++.

- <td>
+ <td width="535">
 Replace text "is
 publicly derived from" with "shall be implemented in a
 manner indistinguishable from". This places an ABI
@@ -3530,23 +3539,23 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 DE-6

 <td>
 5.1.1, 20.7.18

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 DE-6 Some uses of lambda expressions refer to
 specializations of the unconstrained class template
 std::reference_closure (5.1.1). If the lambda expression
@@ -3554,80 +3563,80 @@
 parameter type for the lambda depend on a template
 parameter (see 14.10), such a use is ill-formed.

- <td>
+ <td width="535">
 In 20.7.18, for the class template
 std::reference_closure, require Returnable for R and
 VariableType for each of the ArgTypes.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 DE-7

 <td>
 5.1.1

- <td>
+ <td width="107">
 p10

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 DE-7 The note at the end of paragraph 10 appears to be
 garbled.

- <td>
+ <td width="535">
 Remove "or references" in the note.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 DE-8

 <td>
 5.1.1

- <td>
+ <td width="107">
 p10

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 DE-8 The construction of the function call operator
 signature is missing specifications for the ref-qualifier
 and the attribute-specifier.

- <td>
+ <td width="535">
 Add bullets that say that the ref-qualifier and the
 attribute-specifier are absent.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 33

 <td>
 5.1.1

- <td>
+ <td width="107">
 11

- <td>
+ <td width="38">
 Ge

- <td>
+ <td width="510">
 There is no definition of “move constructor”
 or “move operation”

- <td>
+ <td width="535">
 Since this is
 the first place the terms are used, a definition should
@@ -3635,23 +3644,23 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 DE-9

 <td>
 5.1.1

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 DE-9 There is not a single example of a
 lambda-expression in the standard. See also core issue 720
 in WG21 document N2791 "C++ Standard Core Language Active
@@ -3659,51 +3668,51 @@
 http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2008/n2791.html
 .

- <td>
+ <td width="535">
 Add a few well-chosen examples.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 52

 <td>
 5.2

- <td>
+ <td width="107">
 3

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 This paragraph seens out of place,
 assignment expressions are covered in 5.17

- <td>
+ <td width="535">
 Move p3 to subsection 5.17

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 53

 <td>
 5.2.1

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 The definition in p1 makes no allowance for
 overloaded operator[] that treats the expression as a
 simple function call, and does not support the
@@ -3711,30 +3720,30 @@
 definition when describing the use of brace-init-lists
 inside [].

- <td>
+ <td width="535">
 Insert a new p2 describing the changed
 semantics for overloaded operator[]. This should be a note
 to avoid introducing normative text that could potentially
 conflict with the later definiton of these semantics.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 59

 <td>
 5.2.2

- <td>
+ <td width="107">
 7

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 When there is no parameter for a given
 argument, the argument is passed in such a way that the
 receiving function can obtain the value of the argument by
@@ -3742,160 +3751,160 @@
 template <class ... Types> void f(Types ... pack);
 f(1, 2, 3);

- <td>
+ <td width="535">
 Clarify that this sentence only applies
 where the ellipsis is used.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 60

 <td>
 5.2.5

- <td>
+ <td width="107">
 3

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 In the remainder of 5.2.5, cq represents
 either const or the absence of const vq represents either
 volatile or the absence of volatile.

- <td>
+ <td width="535">
 Add "and" before vq

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 61

 <td>
 5.2.5

- <td>
+ <td width="107">
 p1

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 Together with footnote 60 there may be
 confusion that the postfix expression is always evaluated -
 even when part of an unevaluated operand. We believe the
 standard does not require this, and a comment in the
 existing note would be a useful clarification.

- <td>
+ <td width="535">
 Clarify in footnote 60 that this will not
 happen if the whole expression is an unevaluated operand.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 62

 <td>
 5.2.5

- <td>
+ <td width="107">
 4

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 In the final bullet, what does 'not an
 lvalue' mean? Does it imply rvalue, or are there other
 possible meanings? Should clauses that trigger on rvalues
 pick up on this?

- <td>
+ <td width="535">
 Replace 'not an lvalue' with 'is an
 rvalue'.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 DE-10

 <td>
 5.2.5

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 DE-10 If E1.E2 is referring to a non-static member
 function, the potential ref-qualification on E2 should be
 taken into account.

- <td>
+ <td width="535">
 Adjust the presentation of the types involved as
 appropriate.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 63

 <td>
 5.2.6

- <td>
+ <td width="107">
 2

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 Paragraph 2 is missing its number.

- <td>
+ <td width="535">
 Add one.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 64

 <td>
 5.2.7

- <td>
+ <td width="107">
 3

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 A new name R is introduced for use in
 paragraphs 3 and 4. But R is the same as T.

- <td>
+ <td width="535">
 Replace R with T
 and replace "the required result type (which, for
 convenience, will be called R in this description)" with
@@ -3903,24 +3912,24 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 65

 <td>
 5.2.7

- <td>
+ <td width="107">
 8

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 In the first two
 bullets we have "the result is a pointer (an lvalue
 referring) to". But para 2 makes clear that a dynamic_cast
@@ -3929,60 +3938,60 @@

 

- <td>
+ <td width="535">
 Replace "an lvalue referring to" with
 "reference", twice.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 66

 <td>
 5.2.8

- <td>
+ <td width="107">
 1

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 typeid may
 return "an implementation-defined class derived from std ::
 type_info". The derivation must be public.

 

- <td>
+ <td width="535">
 an implementation-defined class publicly
 derived from std :: type_info

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 67

 <td>
 5.2.9

- <td>
+ <td width="107">
 1, 2, 3

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 Paragraph 1 specifies when the result of
 static_cast is an lvalue; repeating it is unnecessary.

- <td>
+ <td width="535">
 In para 2,
 delete "It is an lvalue if the type cast to is an lvalue
 reference; otherwise, it is an rvalue." and "The result is
@@ -3992,30 +4001,30 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 54

 <td>
 5.2.10

- <td>
+ <td width="107">
 3, 6

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 Para 3: "The mapping performed by
 reinterpret_cast is implementation-defined.". Para 6: "...
 the result of such a pointer conversion is unspecified."
 Which is it?

- <td>
+ <td width="535">
 In para 6,
 replace unspecified with implementation-defined.
 Alternatively, delete paragraph 3, since individual cases
@@ -4023,30 +4032,30 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 55

 <td>
 5.2.10

- <td>
+ <td width="107">
 2

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 dynamic_cast and reinterpret_cast
 crossreference 5.2.11 without creating an extra note. The
 second half of the note is unrelated to the crossrefernce,
 and would serve as well in normative text.

- <td>
+ <td width="535">
 Strike the note
 about definition of casting away constness, preserve the
 cross-reference. The second sentance on reintrepret_cast to
@@ -4055,24 +4064,24 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 56

 <td>
 5.2.10

- <td>
+ <td width="107">
 5

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 The notion of
 safely derived pointers means this conversion may not be as
 safe in the revised standard as the original. It would be
@@ -4081,58 +4090,58 @@

 

- <td>
+ <td width="535">
 Add: [Note: the result of such a conversion
 will not be a safely-derived pointer value (3.7.4.3) -- end
 note]

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 57

 <td>
 5.2.10

- <td>
+ <td width="107">
 8

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 Conditionally supported behaviour gives a
 wide range or permission, so clarify relationship between
 safely-derived object pointers and function pointers in a
 note.

- <td>
+ <td width="535">
 Add: [Note: In such cases, the
 implementation shall also define whether a safely-derived
 object pointer cast to a function pointer can be safely
 cast back -- end note]

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 58

 <td>
 5.2.11

- <td>
+ <td width="107">
 9

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 Casting from an
 lvalue of type T1 to an lvalue of type T2 using a reference
 cast casts away constness if a cast from an rvalue of type
@@ -4142,15 +4151,15 @@

 

- <td>
+ <td width="535">
 Replace lvalue with "lvalue or rvalue"
 twice.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US
 34

@@ -4159,65 +4168,65 @@
 <td>
 5.3

- <td>
+ <td width="107">
 1

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 The list of unary operator
 should be in teletype font.

- <td>
+ <td width="535">
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 68

 <td>
 5.3.1

- <td>
+ <td width="107">
 2-9

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 All the unary operands other than * return
 rvalues - but this is not stated.

- <td>
+ <td width="535">
 Add a paragraph
 1a "The following unary operators all produce results that
 are rvalues."

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 69

 <td>
 5.3.1

- <td>
+ <td width="107">
 2

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 If we cannot
 bind references/take address of functions in concept_maps,
 does that mean we cannot use generic bind in constrained
@@ -4231,27 +4240,27 @@

 

- <td>
+ <td width="535">
 ... unknown ...

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 70

 <td>
 5.3.3

- <td>
+ <td width="107">
 1

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 The sizeof
 operator shall not be applied to ... an enumeration type
 before all its enumerators have been declared We should
@@ -4259,28 +4268,28 @@

 

- <td>
+ <td width="535">
 Change "an enumeration type" to "an
 enumeration type whose underlying type is not fixed".

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 71

 <td>
 5.3.4

- <td>
+ <td width="107">
 2

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 The type of an allocated object wih the
 type specifier auto is determined by the rules of copy
 initialization, but the initialization applied will be
@@ -4289,27 +4298,27 @@
 consistency, use the same form of initiailization for the
 deduction as the new expression.

- <td>
+ <td width="535">
 Replace T x = e; with T x(e);

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 72

 <td>
 5.3.4

- <td>
+ <td width="107">
 7

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 The library
 headers have been carefully structured to limit the
 dependencies between core language and specific headers.
@@ -4322,28 +4331,28 @@

 

- <td>
+ <td width="535">
 Throw std::bad_alloc instead of
 std::length_error.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 73

 <td>
 5.3.4

- <td>
+ <td width="107">
 6

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 A class type
 with conversion operator can only be used if the conversion
 type is constexpr and the class is a literal type. Adding
@@ -4352,27 +4361,27 @@

 

- <td>
+ <td width="535">
 Add 'literal' before 'class type'

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 74

 <td>
 5.3.4

- <td>
+ <td width="107">
 8

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 operators, like
 constructors and destructors, do not have names. However,
 in certain circumstances they can be treated as if they had
@@ -4381,105 +4390,105 @@

 

- <td>
+ <td width="535">
 Change "the allocation function’s
 name is operator new" to "the allocation function is named
 operator new" and similarly for operator delete.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 35

 <td>
 5.3.4

- <td>
+ <td width="107">
 9

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 Missing period in middle of paragraph
 between "in the scope of T" and "If this lookup fails"

- <td>
+ <td width="535">
 Add a period
 between "in the scope of T" and "If this lookup fails"

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 75

 <td>
 5.3.5

- <td>
+ <td width="107">
 8

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 A paragraph
 strarting with [Note... is easily skipped when reading,
 missing the normative text at the end.

 

- <td>
+ <td width="535">
 Swap order of the note and normative text.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 FR 21

 <td>
 5.3.6 [Alignof

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 Should not the type of alignof-expression be of type
 std::max_align_t?

- <td>
+ <td width="535">
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 35

 <td>
 5.8

- <td>
+ <td width="107">
 2 and 3

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 
 There is curious spacing in the expressions "E1 <<E2"
 and "E1 >>E2". This is a formatting change since
@@ -4487,27 +4496,27 @@

 

- <td>
+ <td width="535">
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 47

 <td>
 5.14 / 5.15

- <td>
+ <td width="107">
 2

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 Why are the
 descriptions of order of evaluation of expressions and side
 effects different between && and || operators. The
@@ -4517,28 +4526,28 @@

 

- <td>
+ <td width="535">
 Pick one form of wording as 'the best' and
 apply it in both places.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 48

 <td>
 5.18

- <td>
+ <td width="107">
 1

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 The defining
 feature of the comma operator is the guaranteed sequencing
 of two expressions. This guarantee is lost when presented
@@ -4547,36 +4556,36 @@

 

- <td>
+ <td width="535">
 Add: [Note: There are no guarantees on the
 order of value computation for an overloaded comma operator
 -- end note]

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 49

 <td>
 5.19

- <td>
+ <td width="107">
 2

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 Is an implementation permitted to reject
 this? constexpr int f() { return f(); } int a[f()]; AFAICT
 it is well-formed; f() seems to satisfy all the rules to
 make it a constant expression. I would hate compilation to
 become a potentially non-terminating experience.

- <td>
+ <td width="535">
 Add an escape
 clause to allow the implementation to reject excessively
 deep nesting of constexpr function evaluations. (This can
@@ -4588,54 +4597,54 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 50

 <td>
 5.19

- <td>
+ <td width="107">
 2

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 The following should be valid: enum E { foo
 = 4}; const E c = foo; int a[c]; But currently it is not -
 c is not an lvalue of effective integral type (4th bullet).
 (See also 7.1.6.1/2)

- <td>
+ <td width="535">
 Change
 "effective integral type" to "effective integral or
 enumeration type" in the 4th bullet, 1st sub-bullet.

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 51

 <td>
 5.19

- <td>
+ <td width="107">
 2

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 typeid
 expressions can never be constant, whether or not the
 operand is a polymorphic class type. The result of the
@@ -4645,56 +4654,58 @@

 

- <td>
+ <td width="535">
 Strike the words "whose operand is of a
 polymorphic class type" on the bullet for typeid
 expressions.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 76

 <td>
 6.3

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 Do we really need two different terms that
 say the same thing?

- <td>
+ <td width="535">
 Pick either
 'block' or 'compound statement' as the preferred term and
 use it consistently throughout the standard.

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 FR 22

 <td>
- 6.4.2 [The switch statement]
+ 6.4.2 
+ [The switch 
+ statement]

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 The constant-expression in

 
@@ -4712,27 +4723,27 @@

 

- <td>
+ <td width="535">
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 77

 <td>
 6.5

- <td>
+ <td width="107">
 5

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 The terms i/o
 operation, synchronize operation and atomic operation have
 very specific meanings within the standard. The paragraph
@@ -4741,34 +4752,34 @@

 

- <td>
+ <td width="535">
 Profide a cross-reference for the terms:
 i/o operation, synchronize operation and atomic operation

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 11

 <td>
 6.5.4

- <td>
+ <td width="107">
 1st para, 5th
 line

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 There is no _RangeT type in the equivalent code to
 “range-base for” statement. It existed in
 N2049.

- <td>
+ <td width="535">
 Add
 a typedef for _RangeT in the example as follows:

@@ -4818,29 +4829,29 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 78

 <td>
 6.5.4

- <td>
+ <td width="107">
 2

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 Including the header
 <iterator_concepts> is far too unwieldy to enable an
 important and (expected to be) frequently used syntax.

- <td>
+ <td width="535">
 Merge
 <iterator_concepts> into <concepts> and change
 6.5.4p2 to refer to <concepts>, or make the Range
@@ -4849,24 +4860,24 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 79

 <td>
 6.5.4

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 The definition
 of for (for-range-declaration : expression) statement is
 expanded in terms which require a Range concept, and the
@@ -4879,7 +4890,7 @@

 

- <td>
+ <td width="535">
 When expression is an array a of length N
 whose length is known at compile time, expand range-for as
 'for (... p=a, p!=a+N, p++) ...' without requiring the
@@ -4887,23 +4898,23 @@
 expression is an initializer_list, expand range-for
 similarly without requiring <iterator_concepts>.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 DE-11

 <td>
 6.9

- <td>
+ <td width="107">
 p1

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 DE-11 A
 sentence in paragraph 1 reads: "Outside of a constrained
@@ -4914,28 +4925,28 @@

 

- <td>
+ <td width="535">
 State that such a late-checked block has the same
 meaning as if the late_check keyword were absent.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 80

 <td>
 7

- <td>
+ <td width="107">
 1

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 Many of the
 sections and major subsections open with a sentence
 summarising the content. I'm not sure this is necessary;
@@ -4949,27 +4960,27 @@

 

- <td>
+ <td width="535">
 Strike the first sentence.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 81

 <td>
 7

- <td>
+ <td width="107">
 4

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 String literal
 concatenation happens in phase 6, before parsing, so it is
 legal and useful to use it for the string literal in a
@@ -4978,29 +4989,29 @@

 

- <td>
+ <td width="535">
 Add a note: Multiple adjacent string
 literals may be used instead of a single /string-literal/;
 see [lex.phases].

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 82

 <td>
 7

- <td>
+ <td width="107">
 2

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 Paragraph 2
 talks about declarations that can have nested declarations
 within them. It doesn't mention scoped enumerations - but
@@ -5009,28 +5020,28 @@

 

- <td>
+ <td width="535">
 Add "scoped enumeration" to the list in the
 second sentence.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 83

 <td>
 7.1

- <td>
+ <td width="107">
 2

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 The longest
 sequence of decl-specifiers that could possibly be a type
 name is taken as the decl-specifier-seq of a declaration.
@@ -5039,28 +5050,28 @@

 

- <td>
+ <td width="535">
 Not sure. I understand the rule, just not
 how to say it.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 84

 <td>
 7.1

- <td>
+ <td width="107">
 1

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 The grammar
 includes alignment-specifier as a production for
 decl-specifier, but there is no production for
@@ -5069,27 +5080,27 @@

 

- <td>
+ <td width="535">
 Delete the production (including the
 duplicate in A6)

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 FI 3

 <td>
 7.1

- <td>
+ <td width="107">
 [dcl.spec.auto]

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 While
 it’s considered too late for this standard revision,
@@ -5099,27 +5110,27 @@

 

- <td>
+ <td width="535">
 See restricted-auto.ppt

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 85

 <td>
 7.1.1

- <td>
+ <td width="107">
 1

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 ... the
 init-declarator-list of the declaration shall not be empty
 (except for global anonymous unions, which shall be
@@ -5130,27 +5141,27 @@

 

- <td>
+ <td width="535">
 Replace "global" with "namespace scope".

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 86

 <td>
 7.1.1

- <td>
+ <td width="107">
 2,3

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 The register
 keyword serves very little function, offering no more than
 a hint that a note says is typically ignored. It should be
@@ -5161,28 +5172,28 @@

 

- <td>
+ <td width="535">
 Deprecate current usage of the register
 keyword.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 87

 <td>
 7.1.1

- <td>
+ <td width="107">
 1, 4, 5

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 Why require two
 keywords, where one on its own becomes ill-formed?
 thread_local should imply 'static' in this case, and the
@@ -5192,55 +5203,55 @@

 

- <td>
+ <td width="535">
 Drop requirement to combine static keyword
 with thread_local at block-scope inside a function
 definition.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 36

 <td>
 7.1.1

- <td>
+ <td width="107">
 4

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 The
 permission to use thread_local static data members is
 missing.

 

- <td>
+ <td width="535">
 Add the static members as a
 permitted use.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 FR 23

 <td>
 7.1.5 [constexpr]

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 'constexpr' functions should
 be allowed to take const reference parameters, as long as
 their uses are in a context where a constant expression may
@@ -5262,26 +5273,26 @@

 

- <td>
+ <td width="535">
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 12

 <td>
 7.1.5

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 It should be
 allowed to define constexpr recursively.
@@ -5412,29 +5423,29 @@
 
 

- <td>
+ <td width="535">
 
 Allow constexpr recursion.

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 37

 <td>
 7.1.6.1

- <td>
+ <td width="107">
 1

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 
 There is a "Note: 3.9.3 describes how cv-qualifiers affect
 object and function types." So far as I can see, 3.9.3
@@ -5444,27 +5455,27 @@

 

- <td>
+ <td width="535">
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 89

 <td>
 7.1.6.1

- <td>
+ <td width="107">
 2

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 The two
 normative sentences in this paragraph appear to duplicate
 text elsewhere - but they aren't exact duplicates, which
@@ -5491,29 +5502,29 @@

 

- <td>
+ <td width="535">
 Make the normative text in this section
 into one or more notes, with cross references, and correct
 the referenced text if necessary.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 90

 <td>
 7.1.6.2

- <td>
+ <td width="107">
 para 1 and table 9

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 The grammar in
 paragraph one makes "nested-name-specifier template
 simple-template-id" a simple-type-specifier, but unlike all
@@ -5521,29 +5532,29 @@

 

- <td>
+ <td width="535">
 Add a row to table 9 mentioning
 simple-template-id and punting to clause 14 (cf
 decltype(expression)).

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 91

 <td>
 7.1.6.2

- <td>
+ <td width="107">
 4

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 5.1/5 says "[A]
 parenthesized expression can be used in exactly the same
 contexts as those where the enclosed expression can be
@@ -5561,30 +5572,30 @@

 

- <td>
+ <td width="535">
 Insert "unparenthised" in the first bullet
 point - "if e is an *unparenthised* id-expression ...". In
 the second bullet point, move "(parentheses around e are
 ignored)" into a note.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 92

 <td>
 7.1.6.3

- <td>
+ <td width="107">
 2

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 The note
 correctly indicates that, if T is a template type
 parameter, then "friend class T;" is ill-formed. It might
@@ -5593,28 +5604,28 @@

 

- <td>
+ <td width="535">
 Either strike the note or add reference to
 11.4/3 and/or mention of "friend T;".

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 93

 <td>
 7.1.6.3

- <td>
+ <td width="107">
 Grammar before para 1

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 In the third
 production, "enum ::opt nested-name-specifieropt
 identifier", enum should not be in italics; its referring
@@ -5622,34 +5633,34 @@

 

- <td>
+ <td width="535">
 Change to keyword font

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 94

 <td>
 7.1.6.4

- <td>
+ <td width="107">
 1

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 The auto type-specifier signifies that the
 type of an object being declared shall be deduced from its
 initializer or specified explicitly at the end of a
 function declarator. A function declarator does not declare
 an object.

- <td>
+ <td width="535">
 The auto
 type-specifier signifies that the type of an object being
 declared shall be deduced from its initializer or that the
@@ -5658,24 +5669,24 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 95

 <td>
 7.1.6.4

- <td>
+ <td width="107">
 4

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 (See also
 c++std-core-13583) This paragraph allows auto "in the
 type-specifier-seq in a new-type-id (5.3.4)" (and nowhere
@@ -5689,27 +5700,28 @@

 

- <td>
+ <td width="535">
 Change "in a new-type-id" to "in a
 new-type-id or type-id in a new-expression".

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 FR 24

 <td>
- 7.1.6.4 [auto specifier]
+ 7.1.6.4 
+ [auto specifier]

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 Now that 'auto' is finally
 used in its most obvious sense to state `deduce the type of
 this variable from initializer', it should also be allowed
@@ -5758,52 +5770,52 @@

 

- <td>
+ <td width="535">
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 38

 <td>
 7.2

- <td>
+ <td width="107">
 1

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 The
 discussion of attribute specifiers should be a separate
 paragraph.

 

- <td>
+ <td width="535">
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 39

 <td>
 7.2

- <td>
+ <td width="107">
 2

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 The
 paragraph says in part "An opaque-enum-declaration
 declaring an unscoped enumeration shall not omit the
@@ -5814,28 +5826,28 @@

 

- <td>
+ <td width="535">
 As this implication leaves no
 representation, it should be either affirmed here or the
 statement should be expanded. Perhaps a note is warranted.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 13

 <td>
 7.2

- <td>
+ <td width="107">
 para 3

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 In
 the description for an unscoped enumeration, enum-base in
 redeclaration must be the same underlying type as in the
@@ -5845,28 +5857,28 @@

 

- <td>
+ <td width="535">
 Replace the description, "same underlying type", with
 "same as underlying type of (previous) declaration."

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 96

 <td>
 7.2

- <td>
+ <td width="107">
 7

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 enum E { }; What
 are the values of E? It has neither a smallest nor largest
 enumerator, so paragraph 7 doesn't help. (Paragraph 6
@@ -5876,29 +5888,29 @@

 

- <td>
+ <td width="535">
 Add a second sentence to paragraph 7
 (before "Otherwise"): "If the enumerator-list is empty, 0
 is the only value of the enumeration."

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 97

 <td>
 7.2

- <td>
+ <td width="107">
 9

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 Missing
 punctuation after "blue" in: "The possible values of an
 object of type color are red, yellow, green, blue these
@@ -5906,29 +5918,29 @@

 

- <td>
+ <td width="535">
 Add a semicolon: "The possible values of an
 object of type color are red, yellow, green, blue; these
 values can be converted ..."

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 98

 <td>
 7.2

- <td>
+ <td width="107">
 5

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 It would be
 useful to be able to determine the underlying type of an
 arbitrary enumeration type. This would allow safe casting
@@ -5939,28 +5951,28 @@

 

- <td>
+ <td width="535">
 Add a TransformationTrait to 20.5.6 that
 returns the underlying type of an enumeration type.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 99

 <td>
 7.2

- <td>
+ <td width="107">
 3

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 It is unclear
 whether an enumeration type is complete after an
 opaque-enum-declaration. This paragraph only says so in a
@@ -5970,28 +5982,28 @@

 

- <td>
+ <td width="535">
 Move "an enumeration declared by an
 opaque-enum-declaration ... is a complete type" from the
 note to normative text.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 14

 <td>
 7.3.1

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 
 The description of the behavior when a member that was
@@ -6063,7 +6075,7 @@
 
 

- <td>
+ <td width="535">
 
 Add the description of the behavior when a member that was
@@ -6071,24 +6083,24 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 100

 <td>
 7.3.3

- <td>
+ <td width="107">
 10 and 13

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 Para 10 says "A
 using-declaration is a declaration and can therefore be
 used repeatedly where (and only where) multiple
@@ -6100,28 +6112,28 @@

 

- <td>
+ <td width="535">
 Delete para 10, moving its example into
 para 13.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 101

 <td>
 7.3.3

- <td>
+ <td width="107">
 20

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 If a
 using-declaration uses the keyword typename and specifies a
 dependent name (14.6.2), the name introduced by the
@@ -6133,27 +6145,27 @@

 

- <td>
+ <td width="535">
 Allow typename for non-dependent names iff
 they refer to a type.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 DE-12

 <td>
 7.3.3

- <td>
+ <td width="107">
 p15

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 DE-12
 Overriding and hiding of member functions named in
@@ -6162,30 +6174,32 @@

 

- <td>
+ <td width="535">
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 FR 25

 <td>
- 7.3.3 [The using declaration]
+ 7.3.3 
+ [The using 
+ declaration]

- <td>
+ <td width="107">
 Para 21

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 The syntax for concept map alias is unnecessarily both
 confused and verbose.

- <td>
+ <td width="535">
 We strongly suggest
 simplifications, e.g.

@@ -6197,24 +6211,24 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 102

 <td>
 7.3.4

- <td>
+ <td width="107">
 6

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 This paragraph
 says "If name lookup finds a declaration for a name in two
 different namespaces, and the declarations do not declare
@@ -6224,27 +6238,27 @@

 

- <td>
+ <td width="535">
 Move the example to paragraph 7, and/or
 replace it with an appropriate example.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 40

 <td>
 7.6

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 The
 list of attributes is missing an attribute to indicate that
 a function with a 

- <td>
+ <td width="535">
 Add the attribute.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 41

 <td>
 7.6

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 A
 common problem is unintentionally declaring a new virtual
 member function instead of overriding a base virtual member
@@ -6283,76 +6297,76 @@

 

- <td>
+ <td width="535">
 An attribute stating intent to
 override would enable better diagnostics.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 FR 26

 <td>
 7.6 [Attributes]

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 Are they part of object types
 or not? The section does not appear to indicate that
 clearly.

 

- <td>
+ <td width="535">
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 FI 1

 <td>
 7.6

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 Add override-attribute for functions in order to avoid
 mistakes when overriding functions.

- <td>
+ <td width="535">
 See override-attribute.doc, override-attribute.ppt

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 FR 27

 <td>
 7.6.1

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 This section specifies that
 no name lookup is performed on any identifier contained in
 an attribute-token. This in particular implies that, for
@@ -6370,27 +6384,27 @@

 

- <td>
+ <td width="535">
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 103

 <td>
 7.6.1

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 Attributes should support pack expansion.
 For example, this would be extremely useful with the align
 attribute, directly supporting the (removed) functionality
@@ -6400,29 +6414,29 @@
 this support to attributes would remove the remaining need,
 and support similar attributes in the future.

- <td>
+ <td width="535">
 Add: attribute... to the grammar for
 attribute-list Add to list in 14.5.3p4: "In an
 attribute-list(7.6.1); the pattern is an attribute."

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 104

 <td>
 7.6.1

- <td>
+ <td width="107">
 1

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 It is helpful
 for each subclause to contain a short paragraph introducing
 its intent an purpose. 7.6 has such a paragraph, but it is
@@ -6430,79 +6444,79 @@

 

- <td>
+ <td width="535">
 7.6.1p1 should move up one level to become
 7.6p1. There grammar should remain under 7.6.1

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 105

 <td>
 7.6.1

- <td>
+ <td width="107">
 1

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 Allowing only one level of namespaces in
 attributes seems unnecessarily limiting.

- <td>
+ <td width="535">
 To: attribute-scoped-token:
 attribute-namespace :: identifier add attribute-namespace
 :: attribute-scoped-token

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 106

 <td>
 7.6.2

- <td>
+ <td width="107">
 1

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 Extensive use of
 alignment and related terms without cross reference.

 

- <td>
+ <td width="535">
 Add cross-reference to 3.11.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 15

 <td>
 7.6.2

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 An abbreviation
 of 7.6.2 should be “[decl.attr.align]” instead
@@ -6517,27 +6531,27 @@

 

- <td>
+ <td width="535">
 Change "[dcl.align]" of 7.6.2 to "[decl.attr.align]".

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 107

 <td>
 7.6.3

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 While undefined
 behaviour might be the best we can guarantee, it would be
 helpful to encourage implementations to diagnose function
@@ -6545,30 +6559,30 @@

 

- <td>
+ <td width="535">
 Adda a [Note : implementations are
 encouraged to issue a diagnostic where the definition of a
 function marked [[noreturn]] might execute a return
 statement -- end note]

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 108

 <td>
 7.6.4

- <td>
+ <td width="107">
 2

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 It is unclear
 why no diagnostic is required for an easily detectable
 violation. It is even more surprising that the associated
@@ -6576,27 +6590,27 @@

 

- <td>
+ <td width="535">
 Strike "no diagnostic required" and the
 associated footnote.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 42

 <td>
 7.6.4

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 The
 meaning of the <code>[[final]]</code> attribute applied
@@ -6605,7 +6619,7 @@

 

- <td>
+ <td width="535">
 
 Modify the semantics of <code>[[final]]</code> applied to
@@ -6616,74 +6630,74 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 109

 <td>
 7.6.5

- <td>
+ <td width="107">
 4

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 The example code
 refers in comments to "Compilation unit" A and B. The term
 should be "Translation unit" (2/1)

 

- <td>
+ <td width="535">
 Replace "Compilation" with "Translation" in
 two places

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 

 <td>
 

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 

- <td>
+ <td width="510">
 

- <td>
+ <td width="535">
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 110

 <td>
 7.6.5

- <td>
+ <td width="107">
 4

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 The code in the
 example (compilation unit A) has:
 "foo_head[i].load(memory_order_consume)". foo_head[i] is of
@@ -6691,27 +6705,27 @@

 

- <td>
+ <td width="535">
 Change the type of foo_head to
 atomic<foo *>[].

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 43

 <td>
 8

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 
 With the introduction of late-specified return types for
 functions and lambda expressions, we now have three
@@ -6723,81 +6737,81 @@

 

- <td>
+ <td width="535">
 Some simplification is needed.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 111

 <td>
 8.3.5

- <td>
+ <td width="107">
 13

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 Example missing
 closing bracket in template<typename... T> void f(T
 (* ...t)(int, int);

 

- <td>
+ <td width="535">
 Add closing bracket like this:
 template<typename... T> void f(T (* ...t)(int, int));

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 44

 <td>
 8.3.5

- <td>
+ <td width="107">
 13

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 In
 the Example, "template void f(T (* ...t)(int, int);" is
 missing a close parenthesis.

 

- <td>
+ <td width="535">
 It presumably should read:
 "template void f(T (* ...t))(int, int);".

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 45

 <td>
 8.3.5

- <td>
+ <td width="107">
 13

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 At present,
 function parameter packs can only occur at the end of a
 parameter-declaration-list. This restriction unnecessarily
@@ -6842,7 +6856,7 @@
 parameter-declaration-list should be considered non-deduced
 contexts.

- <td>
+ <td width="535">
 In 8.3.5p13,
 remove the sentence “A function
 parameter pack, if present, shall occur at the end of the
@@ -6897,77 +6911,77 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 DE-13

 <td>
 8.4

- <td>
+ <td width="107">
 p2

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 DE-13 The second paragraph, quoting the grammar for the
 declarator of a function declaration, is not considering
 late-specified return types and attributes.

- <td>
+ <td width="535">
 Properly quote the grammar from 8.3.5.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 16

 <td>
 8.5

- <td>
+ <td width="107">
 
 15th para, 1st line

 

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 
 Typo, duplicated "in"

 "The initialization that
 occurs in in the forms"

- <td>
+ <td width="535">
 Remove one.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 46

 <td>
 8.5.3

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 The ability for
 an rvalue reference to bind to an lvalue opens a
 type-safety hole that becomes very dangerous with concepts.
@@ -6996,7 +7010,7 @@

 

- <td>
+ <td width="535">
 Prohibit rvalue
 references from binding to lvalues.

@@ -7032,51 +7046,51 @@
 12.4, 12.8, but restricted to special functions in that
 comment. (See US NN).

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 49

 <td>
 8.5.4

- <td>
+ <td width="107">
 6

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 In the Example, the comments
 could be improved.

- <td>
+ <td width="535">
 See
 the attached paper "Issues with the C++ Standard" under
 "Editorial Issues" and "8.5.4/6".

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 112

 <td>
 9

- <td>
+ <td width="107">
 4-9

- <td>
+ <td width="38">
 Ge

- <td>
+ <td width="510">
 We now have
 concepts that should (or should not?) map to the terms
 described in Clause 9 - these should be at least
@@ -7084,53 +7098,53 @@

 

- <td>
+ <td width="535">
 Add appropriate forward references to
 14.9.4

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 113

 <td>
 9.4.2

- <td>
+ <td width="107">
 3

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 Mis-applied edit from the paper n2756

- <td>
+ <td width="535">
 The term 'constant-initializer' should have
 been struck out when replaced by
 brace-or-equal-initializer. There are two occurrences in
 this paragraph

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 50

 <td>
 12.1, 12.4, 12.8

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 
 Implicitly-declared default constructors, destructors, copy
 constructors, and copy assignment operators are deleted
@@ -7161,7 +7175,7 @@

 

- <td>
+ <td width="535">
 In 12.1p5,
 remove the phrase “or inaccessible from
 the implicitly-declared default 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 FR 28

 <td>
- 12.6.1 [Explicit
- initialization]
+ 12.6.1 
+ [Explicit 
+ initialization]

 

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 This section, in particular the example with `g' appears
 contradictory with the syntax for uniform initialization.

- <td>
+ <td width="535">
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 51

 <td>
 12.6.2

- <td>
+ <td width="107">
 2

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 The
 discussion of delegating constructors should be in its own
 paragraph.

 

- <td>
+ <td width="535">
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 114

 <td>
 12.6.2

- <td>
+ <td width="107">
 1

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 Despite all the attempts to unify
 initialization syntax, it is still not possible to
 copy-initialize base classes or non-static data members,
@@ -7272,7 +7287,7 @@
 mem-initializer-id and braced-init-list would allow the
 user to choose between copy and direct initialization

- <td>
+ <td width="535">
 Ammend the
 grammar for mem-initializer: mem-initializer-id =OPT
 braced-init-list Extend p3 to allow for Copy Initialization
@@ -7287,46 +7302,46 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 52

 <td>
 13.5.8

- <td>
+ <td width="107">
 ¶ 5

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 A word is misspelled.

- <td>
+ <td width="535">
 Change “shal” to “shall”.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 115

 <td>
 14

- <td>
+ <td width="107">
 6-11

- <td>
+ <td width="38">
 Ge

- <td>
+ <td width="510">
 Exported
 templates were a great idea that is generally understood to
 have failed. In the decade since the standard was adopted,
@@ -7341,30 +7356,30 @@

 

- <td>
+ <td width="535">
 Consider deprecating exported templates,
 but no action yet. Examine interaction with constrained
 templates, and see if other more appropriate mechanism will
 support compile-time optimization.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 116

 <td>
 14

- <td>
+ <td width="107">
 6-11

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 Is it possible
 to export a concept map template? The current wording
 suggests it is possible, but it is not entirely clear what
@@ -7372,29 +7387,29 @@

 

- <td>
+ <td width="535">
 Either prohibit exporting concept map
 templates, or more directly address what it means to export
 a concept map.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 117

 <td>
 14

- <td>
+ <td width="107">
 2

- <td>
+ <td width="38">
 Ge

- <td>
+ <td width="510">
 It would be nice
 to allow template alias within a function scope, and
 possibly a scoped concept map. As these affect name lookup
@@ -7404,28 +7419,28 @@

 

- <td>
+ <td width="535">
 Allow template aliases to be declared
 inside a function scope, and consider scoped concept maps.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 118

 <td>
 14

- <td>
+ <td width="107">
 6-11

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 Exported
 templates are a complicated feature with surprisingly
 little text. To make this important text more visible,
@@ -7433,28 +7448,28 @@

 

- <td>
+ <td width="535">
 Create a new subclause [temp.export]
 containing 14p6-11. Move 14p12 ahead of this subclause.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 119

 <td>
 14

- <td>
+ <td width="107">
 4

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 Does a concept
 map have linkage? Reading this paragraph and 3.5 suggests a
 concept map template has external linkage, but not a
@@ -7464,29 +7479,29 @@

 

- <td>
+ <td width="535">
 Add an exception that concept map templates
 have no linkage, or add concept maps to the list of
 entities with linkage in 3.5

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 120

 <td>
 14.1

- <td>
+ <td width="107">
 9

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 As this is the
 first time the phrase “parameter pack” appears
 in Ch 14 I would like to see the section 8.3.5 referenced
@@ -7494,79 +7509,81 @@

 

- <td>
+ <td width="535">
 Insert “(8.3.5)” after
 “parameter pack”

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 121

 <td>
 14.1

- <td>
+ <td width="107">
 18

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 The example
 (that follows the normative text) has no begin example
 marker

 

- <td>
+ <td width="535">
 Prefix the example code with "[ Example:"

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 FR 29

 <td>
- 14.3 [Template arguments]
+ 14.3 
+ [Template 
+ arguments]

 

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 Constant expressions of any literal type should be
 allowed as template arguments.

- <td>
+ <td width="535">
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 53

 <td>
 14.5.1

- <td>
+ <td width="107">
 5

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 If the
 requirements of a constrained member that is a copy
 constructor, copy assignment operator, or destructor are
@@ -7597,7 +7614,7 @@
 CopyConstructible, vector will get an implicitly-defined
 copy constructor that performs a copy of the pointers.

- <td>
+ <td width="535">
 Add to 14.5.1p5:

 If the constrained member is a copy
@@ -7609,24 +7626,24 @@
 template’s template arguments for its template
 parameters) will be declared as a deleted function (8.4).

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 122

 <td>
 14.5.3

- <td>
+ <td width="107">
 4

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 Variadic
 templates should be supported in axioms. There are axioms
 in the library that rely on this feature, such as the
@@ -7635,29 +7652,30 @@

 

- <td>
+ <td width="535">
 Add clarification in p2 that function
 parameter packs can be used to declare axioms, much like p1
 clarifies they can be used to declare concepts as well as
 templates.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 FR 30

 <td>
- 14.5.7 [Template aliases]
+ 14.5.7 
+ [Template aliases]

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 When are two template alias
 names equivalent?

@@ -7696,28 +7714,28 @@

 

- <td>
+ <td width="535">
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 17

 <td>
 14.7.2

- <td>
+ <td width="107">
 2nd para, 15th
 line

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 
 Typo.

@@ -7742,52 +7760,52 @@

 

- <td>
+ <td width="535">
 Replace "from" with "forming"

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 DE-14

 <td>
 14.7.3

- <td>
+ <td width="107">
 p1

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 DE-14 The bulleted list neither addresses "member
 function template of a class" nor "member class template of
 a class".

- <td>
+ <td width="535">
 Add the respective bullets.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 18

 <td>
 14.7.3

- <td>
+ <td width="107">
 2nd para, 2nd
 line

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 
 Typo,

@@ -7810,28 +7828,28 @@

 

- <td>
+ <td width="535">
 Replace "from" with "forming"

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 19

 <td>
 14.8.2

- <td>
+ <td width="107">
 6th para, 1st
 line

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 
 Typo, duplicated "is"

@@ -7843,152 +7861,153 @@
 
 

- <td>
+ <td width="535">
 
 Remove one

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 54

 <td>
 14.9 [concept],

- 14.10 [temp.constrained]
+ 14.10 
+ [temp.constrained]

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 ge

- <td>
+ <td width="510">
 Concepts is of course the largest new feature in C++0x
 (in terms of new text inserted into the wording), and
 already we have found some significant defects with it. So
 far nothing devastating has been found, but more time is
 needed to shake more bugs out.

- <td>
+ <td width="535">
 I propose no specific change here.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 55

 <td>
 14.9.1

- <td>
+ <td width="107">
 ¶ 6

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 The paragraph number is in the wrong place, causing a
 grammar rule to be indented more than its fellows.

- <td>
+ <td width="535">
 Move the paragraph number so as to follow the grammar
 rules, thus numbering the single sentence, “The body
 of a concept … .”

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 56

 <td>
 14.9.1

- <td>
+ <td width="107">
 ¶ 6

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 The sentence contains two references to 14.9.1.3
 [concept.req].

- <td>
+ <td width="535">
 Change the second such reference (at the end of the
 sentence) to 14.9.1.4 [concept.axiom].

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 57

 <td>
 14.9.1.4

- <td>
+ <td width="107">
 ¶ 3

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 A word is misplaced, changing the intended meaning.

- <td>
+ <td width="535">
 Change “only find … if” to “find
 … only if”.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 58

 <td>
 14.9.1.4

- <td>
+ <td width="107">
 ¶ 3

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 The listed phrases are not grammatically parallel.

- <td>
+ <td width="535">
 Insert “in” before “one” so as
 to obtain “... in the concept, in one of its less
 refined concepts, or in an associated requirement.”

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 59

 <td>
 14.9.1.4

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 Axioms are under-specified and provide
 little benefit to programmers, so they should be removed
 from the working paper. The optimizations permitted by
@@ -8003,7 +8022,7 @@
 that many axioms written by programmers (including those
 specified in the candidate draft) will be incorrect.

- <td>
+ <td width="535">
 Remove clause
 14.9.1.4 [concept.axiom]

@@ -8059,23 +8078,23 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 FR 31

 <td>
 14.9.1.4 [Axioms]

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 This section states that an
 axiom-definition defines a new semantics axiom but is
 unusually vague as to what those semantics might be.
@@ -8100,26 +8119,26 @@

 

- <td>
+ <td width="535">
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 DE-15

 <td>
 14.9.1.4

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 DE-15 There is no implementation experience for axioms.
 Use of axioms is an area of active scientific research. It
 is likely that syntax changes will become necessary to make
@@ -8129,29 +8148,29 @@
 EqualityComparable), but IEEE floating-point types have
 special values such as NaN violating the axioms.

- <td>
+ <td width="535">
 Remove section 14.9.1.4 and any reference to axioms in
 the rest of the proposed standard other than the keyword
 reservation in section 2.11.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 123

 <td>
 14.9.1.4

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 auto concepts
 and axioms are incompatible. An axiom defines the semantics
 of an operaton or set of operations that describes the run
@@ -8163,15 +8182,15 @@

 

- <td>
+ <td width="535">
 Add a paragraph making axioms ill-formed
 inside an auto concept.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 124
@@ -8181,36 +8200,36 @@
 <td>
 14.9.1.4

- <td>
+ <td width="107">
 6

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 Spelling mistake, double-e in were.

- <td>
+ <td width="535">
 weere -> were

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 125

 <td>
 14.9.1.4

- <td>
+ <td width="107">
 2

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 The implicit
 equality comparison operator available to axioms has no
 semantic. It is not clear what expressing the condition if(
@@ -8222,57 +8241,57 @@

 

- <td>
+ <td width="535">
 Define the semantics of the implicitly
 declared comparison operators, or restrict their usage to
 declaring equivalence between statements.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 126

 <td>
 14.9.4

- <td>
+ <td width="107">
 41

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 This paragraph
 contains the only definition of the underlying_type member
 - but it's a note, so not normative.

 

- <td>
+ <td width="535">
 Move the second sentence to the Requires
 clause in paragraph 42.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 127

 <td>
 14.9.4

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 Provide a
 diagram clearly showing refinement relationship between the
 different support concepts. Several were created during
@@ -8280,33 +8299,33 @@

 

- <td>
+ <td width="535">
 Provide the diagram.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 128

 <td>
 14.9.4

- <td>
+ <td width="107">
 4

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 It is surprising for many people that
 non-copyable move-only types can be used with a return
 statement, and so Returnable does not always imply
 CopyConstructible.

- <td>
+ <td width="535">
 A non-normative
 note: [Note: 'move only' types that are constructible from
 rvalue references may be Returnable, but not
@@ -8314,24 +8333,24 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 20

 <td>
 14.9.4

- <td>
+ <td width="107">
 2nd para

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 
 Trivially copyable type was added in “3.9
@@ -8343,29 +8362,29 @@
 "margin-left: 0.2in; text-indent: -0.2in; margin-top: 0.04in">
 

- <td>
+ <td width="535">
 Add
 TriviallyCopyableType that is trivially copyable type as
 concept.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 129

 <td>
 14.10.1, 20.1.2

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 It should be
 possible to support boolean constant expressions as
 requirements without resorting to defining the True concept
@@ -8377,30 +8396,30 @@

 

- <td>
+ <td width="535">
 Remove the True concept and library
 subclause 20.1.2. Provide support in 14.10.1 for boolean
 constant expressions as constraints. This may involve
 overloading the true keyword to disambiguate but ideally
 would not.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 60

 <td>
 14.10.1

- <td>
+ <td width="107">
 1

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 The use of && as the separator for
 a list of requirements has shown itself to be a serious
 teachability problem. The mental model behind
@@ -8413,7 +8432,7 @@
 separator to ‘,’ would eliminate a significant
 source of confusion.

- <td>
+ <td width="535">
 Replace

 
@@ -8451,24 +8470,24 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 130

 <td>
 15.1

- <td>
+ <td width="107">
 4

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 With the new
 crrent_exception API it is possible to capture a reference
 to an exception that will outlive its last active handler.
@@ -8480,56 +8499,56 @@

 

- <td>
+ <td width="535">
 Update sentence to allow for exceptions
 held in excpetion_ptr objects.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 131

 <td>
 15.3

- <td>
+ <td width="107">
 3

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 A handler
 catching its parameter by rvalue-reference is syntactically
 valid, but will never be activated.

 

- <td>
+ <td width="535">
 Disallow handlers catching by
 rvalue-reference.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 132

 <td>
 15.3

- <td>
+ <td width="107">
 16

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 There are
 obscure cases whrere a copy constructor is not usually the
 best match to copy-initialize an object, e.g. A converting
@@ -8541,112 +8560,112 @@

 

- <td>
+ <td width="535">
 Rewite using copy-initialization rather
 than directly invoking the copy constructor

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 133

 <td>
 15.4

- <td>
+ <td width="107">
 2

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 Template aliases
 have the same semantics as a typedef so should also be
 disallowed

 

- <td>
+ <td width="535">
 add "or alias-declaration" after "shall not
 appear in a typedef declaration".

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 134

 <td>
 15.4

- <td>
+ <td width="107">
 6

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 The sentance "An
 exception-specification can also include the class
 std::bad_exception (18.7.2.1)." is redundant.

 

- <td>
+ <td width="535">
 Either strike the quoted sentance, or add a
 note explaining why it is worth calling special attention
 to this class.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 135

 <td>
 15.4

- <td>
+ <td width="107">
 8

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 Unclear if std::unexpected is called before
 or after the function arguments have been destroyed

- <td>
+ <td width="535">
 Clarify the sequence of calling unexpected
 with respect to interesting objects, such as function
 arguments or partially constructed bases and members when
 called from a constructor or destructor

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 136

 <td>
 15.4

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Ge

- <td>
+ <td width="510">
 Exception specifications have proven close
 to worthless in practice, while adding a measurable
 overhead to programs. The feature should be deprecated. The
@@ -8655,7 +8674,7 @@
 requirement to call the runtime unexpected mechanism was
 relaxed in this case.

- <td>
+ <td width="535">
 Move 15.4 and the parts of 15.5 that refer
 to it to Appendix D. Replace 15.4 with a simpler
 specification for empty throw specifications, where the
@@ -8664,24 +8683,24 @@
 checks. Ideally require vendors to provide a mode where the
 runtime checks are always disabled.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 137

 <td>
 15.5

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 There is no
 mention of the current_exception API which can extend the
 lifetime of an exception object. There should at least be a
@@ -8689,57 +8708,57 @@

 

- <td>
+ <td width="535">
 Add another paragraph outlining 18.7.5 and
 the ability of an exception_ptr to extend the lifetime of
 an exception object

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 138

 <td>
 15.5.1

- <td>
+ <td width="107">
 1

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 The third bullet
 is redundant with the first, as it is a subset of the same
 conditions.

 

- <td>
+ <td width="535">
 Merge the third bullet into the first
 bullet as a note or example.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 139

 <td>
 15.5.1

- <td>
+ <td width="107">
 1

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 According to the
 first bullet it is perfectly alright for a library function
 to exit by throwing an exception during stack unwinding,
@@ -8747,28 +8766,28 @@

 

- <td>
+ <td width="535">
 Strike the word 'user' from the first
 bullet point.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 140

 <td>
 15.5.2

- <td>
+ <td width="107">
 2

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 The detailed
 specification can fool people into thinking an exception
 will automatically be translated into bad_exception, where
@@ -8777,103 +8796,103 @@

 

- <td>
+ <td width="535">
 Add a note highlighting the default
 behaviour of std::unexpected if the user does not supply a
 hander-function

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 141

 <td>
 15.6

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 This whole
 subclause is redundant due to 15.1p5 and 15.3p17

 

- <td>
+ <td width="535">
 Strike 15.6

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 142

 <td>
 16.3.5

- <td>
+ <td width="107">
 3

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 This paragraph
 opens with "[ Note" but has no corresponding "end note ]"

 

- <td>
+ <td width="535">
 Add "end note ]"

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 143

 <td>
 16.3.5

- <td>
+ <td width="107">
 7

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 Example uses #define t(x,y.z) x ## y ## z

- <td>
+ <td width="535">
 Change "x,y.z" to "x,y,z"

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 2

 <td>
 17-30

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 ge/te

- <td>
+ <td width="510">
 The
 active issues identified in WG21 N2806, C++ Standard
 Library Active Issues, must be addressed and appropriate
@@ -8889,57 +8908,57 @@

 

- <td>
+ <td width="535">
 Appropriate action would
 include making changes to the CD, identifying an issue as
 not requiring a change to the CD, or deferring the issue to
 a later point in time.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 FR 2

 <td>
 General Comment

- <td>
+ <td width="107">
 Library

- <td>
+ <td width="38">
 ge

- <td>
+ <td width="510">
 The adoption of the library `constexpr' proposal was not
 reflected in the draft, despite formal WG21 committee vote.

- <td>
+ <td width="535">
 FR 2

- <td>
+ <td width="89">
 General Comment

 <tr valign="top">
- <td>
+ <td width="29">
 US 61

 <td>
 17 onward

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 The concepts core language feature is applied to only
 some of the Standard Library clauses, and even then not
 always consistently.

- <td>
+ <td width="535">
 Review all
 clauses of the Standard Library, and consistently apply
@@ -8949,63 +8968,63 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 CA-2

 <td>
 17 Library

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Ge

- <td>
+ <td width="510">
 
 “Concepts” are a significant new addition to
 the language, but are not exploited uniformly in the
 library as documented in CD 14882.

- <td>
+ <td width="535">
 Fix
 the standard library so that “Concepts” are
 used appropriately in the library.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 62

 <td>
 17-30

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 ge

- <td>
+ <td width="510">
 Provide concepts
 and requirements clauses for all standard library templates

 

- <td>
+ <td width="535">
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 63

 <td>
@@ -9013,13 +9032,13 @@

 

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 The behavior of the library in the presence of threads
 is incompletely specified.

@@ -9033,26 +9052,26 @@
 at() to different characters in the same non-const string
 really introduce a data race?

- <td>
+ <td width="535">
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 DE-2

 <td>
 17 through 30

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 DE-2 Marking a constructor with "explicit" has semantics
 even for a constructor with zero or several parameters:
 Such a constructor cannot be used with list-initialization
@@ -9060,17 +9079,17 @@
 standard library apparently has not been reviewed for
 marking non-single-parameter constructors as "explicit".

- <td>
+ <td width="535">
 Consider marking zero-parameter and multi-parameter
 constructors "explicit" in classes that have at least one
 constructor marked "explicit" and that do not have an
 initializer-list constructor.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 21

 <td>
@@ -9083,15 +9102,16 @@
 
 21.2, 21.4,

- 27.2, 27.6, 27.7, 27.8.1, 28.4
+ 27.2, 27.6, 
+ 27.7, 27.8.1, 28.4

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 
 Support of char16_t/char32_t is insufficient. The basic_xxx
 classes of <iostream>, <fstream>,
@@ -9102,7 +9122,7 @@
 Functions such as stoi, to_string in ‘21.4 Numeric
 Conversion’ does not support char16_t/char32_t types.

- <td>
+ <td width="535">
 Add commented
 lines corresponding to char16_t, char32_t.
@@ -9902,125 +9922,125 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 144

 <td>
 17.1

- <td>
+ <td width="107">
 2

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 List of contents of library should be
 extened to cover new clauses

- <td>
+ <td width="535">
 Add "regular expressions, atomic operations
 and threads"

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 145

 <td>
 17.1

- <td>
+ <td width="107">
 6

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 
 Summary of numeric facilities should
 mention random numbers

 

- <td>
+ <td width="535">
 Add random number framework to the list of
 library facilities

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 146

 <td>
 17.1

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 Add a summary paragraph for regular
 expressions

- <td>
+ <td width="535">
 Add a summary paragraph for regular
 expressions

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 147

 <td>
 17.1

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 Add a summary paragraph for threads

- <td>
+ <td width="535">
 Add a summary paragraph for threads

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 148

 <td>
 17.2

- <td>
+ <td width="107">
 Table 12

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 Table 12 is
 mentioned in and relates to section 17.2, but has been
 pushed down to appear directly after the title of section
@@ -10028,57 +10048,57 @@

 

- <td>
+ <td width="535">
 Make sure tables are rendered in the
 section to which they relate.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 149

 <td>
 17.3

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 For consistency
 with narrow-oriented and wide-oriented streams, we should
 add terms for streams of Unicode character sequences

 

- <td>
+ <td width="535">
 Define Utf16-oriented stream classes and
 Uft32-oriented stream classes for streams of
 char16_t/char32_t values.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 150

 <td>
 17.3

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 The addition of move semantics to the
 language means that many library APIs leave an object in a
 safely-destructible state, where no other operations can
@@ -10088,7 +10108,7 @@
 with singular iterators suggest the term 'singular object'
 or 'the object is in a singular state'.

- <td>
+ <td width="535">
 Define 'singular
 state' such that an object with a singular state can only
 be assigned to or safely destroyed. Assiging a new value
@@ -10103,51 +10123,51 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 151

 <td>
 17.3.1

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 Missing
 crossreference to 17.3.17 [defns.repositional.stream]

 

- <td>
+ <td width="535">
 Add cross-reference in the existing empty
 brackets

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 152

 <td>
 17.3.12

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 Object state is
 using a definition of object (instance of a class) from
 outside the standard, rather than the 'region of storage'
@@ -10155,27 +10175,27 @@

 

- <td>
+ <td width="535">
 Clarify terms and usage

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 153

 <td>
 17.3.17

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 If a
 repositional stream can only seek to a position previously
 encountered, then an arbitrary-positional-stream cannot
@@ -10183,15 +10203,15 @@

 

- <td>
+ <td width="535">
 Strike the word 'only'. A note might be
 added to reinforce the intent

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 154
@@ -10201,90 +10221,90 @@
 <td>
 17.3.20

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 Missing definition of a stable partition
 algorithm

- <td>
+ <td width="535">
 Add definition from 25.2.12p7

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 155

 <td>
 17.3.3

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 Add clause 28 to list that use this
 definition of character

- <td>
+ <td width="535">
 Add clause 28 to list that use this
 definition of character

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 156

 <td>
 17.3.4

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 Add regular
 expressions to set of templates using character container
 type

 

- <td>
+ <td width="535">
 Add regular expressions to set of templates
 using character container type

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 157

 <td>
 17.5.2.2

- <td>
+ <td width="107">
 3

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 Add concepts to
 the ordered list of presentation

@@ -10292,82 +10312,82 @@

 

- <td>
+ <td width="535">
 Add concepts into the sequence

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 158

 <td>
 17.5.2.2

- <td>
+ <td width="107">
 3

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 templates are neither classes nor functions

- <td>
+ <td width="535">
 Replace
 'classes' and 'functions' with 'classes and class
 templates' and 'functions and function templates'

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 159

 <td>
 17.5.2.4

- <td>
+ <td width="107">
 Footnote 152

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 This informative
 footnote was relevant in 1998, not 2008. The term 'existing
 vendors' may imply something different now

 

- <td>
+ <td width="535">
 Strike the footnote, or replace 'existing'
 with 'original' or similar

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 160

 <td>
 17.5.2.4

- <td>
+ <td width="107">
 3

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 requires is now
 a keyword with a specific meaning related to concepts, and
 its use in library specifcation may be confusing. Generally
@@ -10379,27 +10399,27 @@

 

- <td>
+ <td width="535">
 Replace 'Requires' with 'Preconditions'

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 161

 <td>
 17.5.2.4

- <td>
+ <td width="107">
 4

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 This paragraph
 is redundant as the definition of the term 'handler
 function' is already provided in 17.3. Are we in danger of
@@ -10408,27 +10428,27 @@

 

- <td>
+ <td width="535">
 Strike 17.5.2.4p4

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 162

 <td>
 17.5.2.4

- <td>
+ <td width="107">
 3

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 Clause 30 makes
 use of a 'Synchronization' semantic element, that
 frequently appears either between Effects: and
@@ -10436,29 +10456,29 @@

 

- <td>
+ <td width="535">
 Add 'Synchronization' to the list either
 between Effects: and Postconditions:, or between Returns:
 and Throws:.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 163

 <td>
 17.5.2.4

- <td>
+ <td width="107">
 3

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 Many functions
 are defined as "Effects: Equivalent to a...", which seems
 to also define the preconditions, effects, etc. But this is
@@ -10466,34 +10486,34 @@

 

- <td>
+ <td width="535">
 Introduce an explicit "Equivalent to",
 which defines all of the properties of the function.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 164

 <td>
 17.5.3.2.1

- <td>
+ <td width="107">
 1

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 This phrasing predates concepts. While this
 kind of description is still used, the examples provided
 are now all concepts, and should be replaced with
 appropriate examples

- <td>
+ <td width="535">
 Use better names
 for the examples. Ideally totally replace the need by
 constraining all templates in library, so that real
@@ -10502,24 +10522,25 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 165

 <td>
- 17.5.3.2.2, 17.5.3.2.3
+ 17.5.3.2.2, 
+ 17.5.3.2.3

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 constraints on
 bitmask and enumation types were supposed to be tightened
 up as part of the motivation for the constexpr feature -
@@ -10527,82 +10548,83 @@

 

- <td>
+ <td width="535">
 Adopt wording in line with the motivation
 described in N2235

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 166

 <td>
- 17.5.3.2.4.1,
- 17.5.3.3
+ 17.5.3.2.4.1, 
+ 17.5.3.3

 

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 List of library clauses should go up to 30,
 not 27

- <td>
+ <td width="535">
 Replace initial refernce to ch27 with ch30

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 167

 <td>
- 17.5.3.4 Private members
+ 17.5.3.4 
+ Private members

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 Comment marker in wrong place.

- <td>
+ <td width="535">
 Change: //
 streambuf* sb; exposition only to streambuf* sb; //
 exposition only To reflect actual usage.

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 168

 <td>
 17.6.2.2

- <td>
+ <td width="107">
 2

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 We should make
 it clear (either by note or normatively) that namespace std
 may contain inline namespaces, and that entities specified
@@ -10613,30 +10635,30 @@

 

- <td>
+ <td width="535">
 Replace "namespace std or namespaces nested
 within namespace std" with "namespace std or namespaces
 nested within namespace std or inline namespaces nested
 directly or indirectly within namespace std"

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 169

 <td>
 17.6.2.2

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 This phrasing
 contradicts later freedom to implement the C standard
 library portions in the global namespace as well as std.
@@ -10644,27 +10666,27 @@

 

- <td>
+ <td width="535">
 Resolve conflict in either place

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 170

 <td>
 17.6.2.3

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 One of goals of
 C++0x is to make language easier to teach and for
 'incidental' programmers. The fine-grained headers of the
@@ -10676,31 +10698,31 @@

 

- <td>
+ <td width="535">
 Add a new header <std> that has the
 effect of including everything in tables 13 and 14, except
 <iosfwd> and <cassert>. Add an additional
 header <fwd> that adds all declarations from
 <std> but no definitions.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 171

 <td>
 17.6.2.4

- <td>
+ <td width="107">
 3

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 Does
 freestanding implementation require a full implementation
 of all listed headers? The reference to abort, at_exit and
@@ -10711,84 +10733,84 @@

 

- <td>
+ <td width="535">
 Either strike the references to abort,
 at_exit and exit, or clarify which headers only require
 partial support.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 172

 <td>
 17.6.2.4

- <td>
+ <td width="107">
 3

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 No reference to
 new functions quick_exit and at_quick_exit

 

- <td>
+ <td width="535">
 Add reference to quick_exit and
 at_quick_exit

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 173

 <td>
 17.6.2.4

- <td>
+ <td width="107">
 table 15

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 
 <initializer_list> is missing from headers required
 in freestanding implementations.

 

- <td>
+ <td width="535">
 Add 18.8, initializer lists,
 <initializer_list>, to the end of the table.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 23

 <td>
 17.6.2.4

- <td>
+ <td width="107">
 2nd para, Table 15

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 There is a
 freestanding implementation including <type_traits>,
@@ -10802,29 +10824,29 @@
 
 

- <td>
+ <td width="535">
 Add
 <type_traits>, <array>, <ration> to Table
 15.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 174

 <td>
 17.6.3.2

- <td>
+ <td width="107">
 3

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 The phrasing is
 mildly ambiguous when using the word 'it' to refer back to
 the header - an unfotunate reading might confuse it with
@@ -10833,136 +10855,136 @@

 

- <td>
+ <td width="535">
 Replace 'the first reference to any of the
 entities declared in that header by the translation unit'
 with 'the first reference to any of the entities that
 header declares in the translation unit'

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 175

 <td>
 17.6.4.2.1

- <td>
+ <td width="107">
 2

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 Local types can
 now be used to instantiate templates, but don't have
 external linkage

 

- <td>
+ <td width="535">
 Remove the reference to external linkage

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 176

 <td>
 17.6.4.3.3

- <td>
+ <td width="107">
 Footnote 175

 

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 Reference to namespace ::std should be
 17.6.4.2

- <td>
+ <td width="535">
 Change referfence from 17.6.4.3 to 17.6.4.2

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 177

 <td>
 17.6.4.3.4

- <td>
+ <td width="107">
 3

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 Sentence is
 redundant as double underscores are reserved in all
 contexts by 17.6.4.3.3

 

- <td>
+ <td width="535">
 Strike the sentence

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 178

 <td>
 17.6.4.8

- <td>
+ <td width="107">
 2

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 The last sentence of the third bullet
 "Operations on such types can report a failure by throwing
 an exception unless otherwise specified" is redundant as
 behaviour is already undefined.

- <td>
+ <td width="535">
 Strike the sentence

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 179

 <td>
 17.6.4.8

- <td>
+ <td width="107">
 2

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 According to the
 4th bullet there is a problem if "if any replacement
 function or handler function or destructor operation throws
@@ -10971,28 +10993,28 @@

 

- <td>
+ <td width="535">
 Replace the word 'throws' with 'propogates'

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 22

 <td>
 17.6.5.7

- <td>
+ <td width="107">
 4th para, 1st
 line

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 The
 statement below describes relation among two or more
 threads using words “between threads”: 
@@ -11006,7 +11028,7 @@
 such case, “among” is preferred instead of
 “between”.

- <td>
+ <td width="535">
 
 Change "between threads" to "among threads".

@@ -11014,24 +11036,24 @@
 There are same cases in 17.6.1 paragraph 2, 17.6.5.7
 paragraph 6, 30.1 paragraph 1, 30.3.1 paragraph 1 also.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 180

 <td>
 17.6.5.10

- <td>
+ <td width="107">
 1, 4

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 It should not be
 possible to strengthen the exception specification for
 virtual functions as this could break user code. Note this
@@ -11042,28 +11064,28 @@

 

- <td>
+ <td width="535">
 Add restriction that exception
 specification of virtual functions cannot be tightened.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 181

 <td>
 17.6.5.10

- <td>
+ <td width="107">
 Footnote 186

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 This footnote is
 wrong. C library functions do not have any exception
 specification, but might be treated as if they had an empty
@@ -11071,29 +11093,29 @@

 

- <td>
+ <td width="535">
 Clarify that this note does not mean the
 functions are genuinely declared with the specification,
 but are treated as-if.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 182

 <td>
 17.6.5.10

- <td>
+ <td width="107">
 Footnote 188

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 It is very
 helpful to assume all exceptions thrown by the standard
 library derive from std::exception. The 'encouragement' of
@@ -11101,27 +11123,27 @@

 

- <td>
+ <td width="535">
 Make this footnote normative

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 184

 <td>
 18 -> 30

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 The new
 alias-declaration syntax is generally easier to read than a
 typedef declaration. This is especially true for complex
@@ -11129,29 +11151,29 @@

 

- <td>
+ <td width="535">
 Replace all typedef declarations in the
 standard library with alias-declarations, except in the
 standard C library.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 24

 <td>
 18

- <td>
+ <td width="107">
 2nd para, Table 16

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 
 Subclauses are listed in Table 16 as:

@@ -11167,7 +11189,7 @@
 "text-indent: 0.06in; margin-top: 0.04in">"18.7 Exception
 handling …".

- <td>
+ <td width="535">
 
 Sort them in the increasing order 
@@ -11184,53 +11206,54 @@
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 25

 <td>
 18.1

- <td>
+ <td width="107">
 
 6th para , last line, SEE ALSO

 

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 
 max_align_t is described in 18.1, so add 3.11 Alignment as
 the reference.

- <td>
+ <td width="535">
 Add
 "3.11, Alignment" to
 SEE ALSO.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 FR 32

 <td>
- 18.2.1 [Numeric limits]
+ 18.2.1 
+ [Numeric limits]

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 The definition of
 numeric_limits<> as requiring a regular type is both
 conceptually wrong and operationally illogical. As we
@@ -11243,30 +11266,30 @@

 

- <td>
+ <td width="535">
 We suggest that a more pragmatic approach, in the spirit
 of C and C++, be taken so that calls to constrained
 function templates are interpreted as assertions on
 *values*, not necessarily semantics assertions on the
 carrier type.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 DE-16

 <td>
 18.2.1

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 DE-16 The class
 template numeric_limits should not specify the Regular
@@ -11281,31 +11304,31 @@

 

- <td>
+ <td width="535">
 Specify a concept requirement with fewer constraints as
 appropriate, for example SemiRegular.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 26

 <td>
 18.2.1.1

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 
 numeric_limits does not use concept.

- <td>
+ <td width="535">
 
 Correct as follows.

@@ -11347,23 +11370,23 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 DE-17

 <td>
 18.2.6

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 DE-17 The class
 type_index should be removed; it provides no additional
@@ -11371,55 +11394,55 @@

 

- <td>
+ <td width="535">
 Specify concept maps for "const type_info *" as required
 by the ordered and unordered containers and remove the
 class type_index.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 185

 <td>
 18.3.1

- <td>
+ <td width="107">
 2

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 There is no
 header <stdint>, it should either be <stdint.h>
 or <cstdint>

 

- <td>
+ <td width="535">
 Replace <stdint> with <cstdint>

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 DE-18

 <td>
 18.4

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 DE-18 The
 proposed C++ standard makes a considerable number of
@@ -11441,31 +11464,31 @@

 

- <td>
+ <td width="535">
 Consider applying the changes proposed in WG21 document
 N2693 "Requirements on programs and backwards
 compatibility", available at
 http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2008/n2693.html
 .

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 186

 <td>
 18.4

- <td>
+ <td width="107">
 Footnote 221

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 What is the
 purpose of this comment? The standard stream objects (cin,
 cerr etc.) have a peculiar lifetime that extends beyond the
@@ -11474,55 +11497,55 @@

 

- <td>
+ <td width="535">
 Remove the footnote

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 187

 <td>
 18.4

- <td>
+ <td width="107">
 9

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 The term "thread
 safe" is not defined nor used in this context anywhere else
 in the standard.

 

- <td>
+ <td width="535">
 Clarify the intended meaing of "thread
 safe"

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 188

 <td>
 18.4

- <td>
+ <td width="107">
 12

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 The function
 _Exit does not appear to be defined in this standard.
 Should it be added to the table of functions
@@ -11530,32 +11553,32 @@

 

- <td>
+ <td width="535">
 Depends on where _Exit comes from

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 189

 <td>
 18.4, 18.7

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 The addition of the [[noreturn]] attribute
 to the language will be an important aid for static
 analysis tools.

- <td>
+ <td width="535">
 The following
 functions should be declared in C++ with the [[noreturn]]
 attribute: abort exit quick_exit terminate unexpected
@@ -11563,29 +11586,31 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 27

 <td>
- 18.4, 18.9, 18.7.2.2, 18.7.3.1
+ 18.4, 18.9, 
+ 18.7.2.2, 
+ 18.7.3.1

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 
 There are Standard library functions that never return to
 the caller. They are explained so in the Standard but not
 declared explicitly.

- <td>
+ <td width="535">
 
 Consider to add the attribute [[noreturn]] to such
 functions,
@@ -11610,58 +11635,58 @@
 
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 190

 <td>
 18.5.1

- <td>
+ <td width="107">
 various

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 It is not entirely clear how the current
 specification acts in the presence of a garbage collected
 implementation.

- <td>
+ <td width="535">
 All deallocation
 functions taking a pointer parameter should have a
 Precondition : ptr is a safely-derived pointer value.

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 191

 <td>
 18.5.1.1

- <td>
+ <td width="107">
 4

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 According to the second bullet, behaviour
 becomes undefined (for lack of a specification) if the user
 has not yet called set_new_handler.

- <td>
+ <td width="535">
 Rephrase the
 second bullet in terms of a new handler being installed,
 and update any definition of handler function necessary to
@@ -11669,24 +11694,24 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 192

 <td>
 18.5.1.2

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 The declared
 signature is not compatible with the current requirement to
 throw std::length_error. It is too late to weaken the
@@ -11696,56 +11721,56 @@

 

- <td>
+ <td width="535">
 Fix 5.3.4p7 by required std::bad_alloc
 rather than std::length_error

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 193

 <td>
 18.5.2.2

- <td>
+ <td width="107">
 2

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 quick_exit has
 been added as a new valid way to terminate a program in a
 well defined way

 

- <td>
+ <td width="535">
 Change 3rd bullet: call either abort(),
 exit() or quick_exit();

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 194

 <td>
 18.6

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 The inclusion of
 type_index and hash<type_index> in <typeinfo>
 brings dependencies into <typeinfo> which are
@@ -11754,28 +11779,30 @@

 

- <td>
+ <td width="535">
 Move type_index and hash<type_index>
 out of <typeinfo> and into a new header,
 <typeindex>.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 28

 <td>
- 18.6, 18.7, 19.1
+ 18.6, 
+ 18.7, 
+ 19.1

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 
 Errors reported by Exception classes are of types char or
 std::string only. For example, std::exception is declared
@@ -11785,31 +11812,31 @@

 

- <td>
+ <td width="535">
 
 Consider other types.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 29

 <td>
 18.7.6

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 
 throw_with_nested does not use concept.

- <td>
+ <td width="535">
 
 Correct as follows.

@@ -11832,55 +11859,55 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 30

 <td>
 18.7.6

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 To
 handle nested exceptions strictly, error information of
 tree structure will be required though, the
 nested_exception does not support tree structure. It is
 insufficient as error handling.

- <td>
+ <td width="535">
 
 Consider nested_exception to support tree structure.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 31

 <td>
 18.7.6

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 It
 is difficult to understand in which case nested_exception
 is applied.

- <td>
+ <td width="535">
 Consider to add
 a sample program which rethrows exception.
@@ -11888,24 +11915,24 @@
 
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 195

 <td>
 18.8

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 The class
 definition of std::initializer_list contains concept-maps
 to Range which should be out of the class, and in
@@ -11915,33 +11942,33 @@

 

- <td>
+ <td width="535">
 Delete the two concept maps from
 std::initializer_list.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 196

 <td>
 18.8.3

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 Concept maps for initializer_list to Range
 should not be in language support headers, but instead in
 iterator concepts.

- <td>
+ <td width="535">
 Remove section
 18.8.3 and put it in 24.1.8.1 instead, so that the
 concept_maps from initializer_list to Range are specified
@@ -11951,30 +11978,30 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 197

 <td>
 19

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 All the exception classes in this clause
 take a std::string argument by const reference. They should
 all be overloaded to accept std::string by rvalue rerefence
 for an efficient move as well.

- <td>
+ <td width="535">
 Provide a
 constructor for every exception class in clause 19
 accepting a std::string by rvalue reference, with the
@@ -11982,23 +12009,23 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 32

 <td>
 19.1

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 
 Messages returned by the member function what() of standard
 exception classes seem difficult to judge.
@@ -12039,34 +12066,34 @@
 
 

- <td>
+ <td width="535">
 
 Consider to add footnote that recommends what() returns
 message easy to recognize what exception was thrown.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 64

 <td>
 19.3

- <td>
+ <td width="107">
 1

- <td>
+ <td width="38">
 Ge

- <td>
+ <td width="510">
 “ See also: ISO C
 7.1.4, 7.2, Amendment 1 4.3.”
 It is unclear why this cross reference is here. Amendment 1
 was to C89, not C99.

- <td>
+ <td width="535">
 Delete this
 cross reference. If necessary, expand the main text to
@@ -12074,23 +12101,23 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 65

 <td>
 20

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 Scoped allocators and
 allocator propagation traits add a small amount of utility
 at the cost of a great deal of machinery. The machinery is
@@ -12098,7 +12125,7 @@
 don't have any obvious connection to allocators, including
 basic concepts and simple components like pair and tuple.

- <td>
+ <td width="535">
 
 Sketch of proposed resolution: Eliminate scoped allocators,
 replace allocator propagation traits with a simple uniform
@@ -12124,29 +12151,29 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 198

 <td>
 20

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 The organization of clause 20 could be
 improved to better group related items, making the standard
 easier to navigate.

- <td>
+ <td width="535">
 20.6.7, 20.6.8,
 20.6.9 and 20.6.10 should be grouped under a section called
 "operator wrappers" or similar. The goal of all 4
@@ -12179,24 +12206,24 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 199

 <td>
 20.1.1, 20.1.2

- <td>
+ <td width="107">
 2

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 The requirement
 that programs do not supply concept_maps should probably be
 users do not supply their own concept_map specializations.
@@ -12208,32 +12235,32 @@

 

- <td>
+ <td width="535">
 Replace the term 'program' with 'user'.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 200

 <td>
 20.1.4

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 All standard library use expects Predicates
 to be CopyConstructible, and this should be recognised
 easily without reatedly stating on every use-case.

- <td>
+ <td width="535">
 Either require
 CopyConstructible<F> as part of Predicate, or create
 a refined concept, StdPredicate, used throughout the
@@ -12242,28 +12269,28 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 201

 <td>
 20.1.5

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 The Consistency axiom for
 LessThanComparable will not compile.

- <td>
+ <td width="535">
 Add a requires
 clause to the Consistency axiomL requires
 HasLessEquals<T> &&
@@ -12273,28 +12300,28 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 33

 <td>
 20.1.5

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 
 LessThanComparable and EqualityComparable don't correspond
 to NaN.

- <td>
+ <td width="535">
 Apply
 concept_map to these concepts at FloatingPointType
@@ -12302,134 +12329,134 @@
 
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 66

 <td>
 20.1.10

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 Application of the "Regular" concept to floating-point
 types appears to be controversial (see long discussion on
 std-lib reflector).

- <td>
+ <td width="535">
 State that the “Regular” concept does not
 apply to floating-point types.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 34

 <td>
 20.2

- <td>
+ <td width="107">
 
 1st para, 4th line

 

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 
 Though N2672 pointed at adding
 "#include<initializer_list>", it isn't reflected.

- <td>
+ <td width="535">
 add
 followings

 
 #include <initializer_list> // for concept_map

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 67

 <td>
 20.2.1

- <td>
+ <td width="107">
 ¶ 5 first sent.

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 Some connective words are missing.

- <td>
+ <td width="535">
 Insert “corresponding to” before “an
 lvalue reference type.”

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 35

 <td>
 20.2.3

- <td>
+ <td width="107">
 
 6th para, 1st line

 

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 
 Typo,

 "stdforward" should be
 "std::forward"

- <td>
+ <td width="535">
 Correct typo.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 202

 <td>
 20.2.4

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 The references
 to pair in the tuple-like access to pair functions qualify
 pair with std::pair even though they are in a namespace std
@@ -12437,53 +12464,53 @@

 

- <td>
+ <td width="535">
 Remove the std:: qualification from these
 references to pair.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 68

 <td>
 20.2.12

- <td>
+ <td width="107">
 IntegralLike

- <td>
+ <td width="38">
 te/ed

- <td>
+ <td width="510">
 The code defining the context is syntactically
 incorrect.

- <td>
+ <td width="535">
 Insert a comma in two places: at the end of the third
 line of refinements, and at the end of the fourth line of
 refinements.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 203

 <td>
 20.3.2

- <td>
+ <td width="107">
 1-4

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 The ratio_xyz
 types have a misplaced '}'. For example: template <class
 R1, class R2> struct ratio_add { typedef see below}
@@ -12491,60 +12518,60 @@

 

- <td>
+ <td width="535">
 Move the '}' to after the typedef: template
 <class R1, class R2> struct ratio_add { typedef see
 below type; };

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 36

 <td>
 20.4.2.1

- <td>
+ <td width="107">
 
 19th para, 6th line

 

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 
 Typo.

 "it
 it" should be "it is"

- <td>
+ <td width="535">
 
 Correct typo.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 204

 <td>
 20.5

- <td>
+ <td width="107">
 Table 41

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 It is not
 possible to create a variant union based on a parameter
 pack expansion, e.g. to implement a classic discriminated
@@ -12552,52 +12579,52 @@

 

- <td>
+ <td width="535">
 Restore aligned_union template that was
 removed by LWG issue 856.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 69

 <td>
 20.5

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 This section, dealing with tuple<>, should be in
 the same section as the similar utility pair<>.

- <td>
+ <td width="535">
 Restructure Clause 20 so as to bring these similar
 components together.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 205

 <td>
 20.5.3

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 
 integral_constant objects should be usable in
 integral-constant-expressions. The addition to the language
@@ -12606,29 +12633,29 @@

 

- <td>
+ <td width="535">
 Add a constexpr conversion operator to
 class tempalate integral_constant: constexpr operator
 value_type() { return value; }

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 206

 <td>
 20.5.5

- <td>
+ <td width="107">
 para 4

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 Currently the
 std says: "In order to instantiate the template
 is_convertible<From, To>, the following code shall be
@@ -12638,7 +12665,7 @@

 

- <td>
+ <td width="535">
 Change: "In order to instantiate the
 template is_convertible<From, To>, the following code
 shall be well formed:" To: "The template
@@ -12646,28 +12673,28 @@
 indirectly from true_type if the following code is well
 formed:"

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 207

 <td>
 20.5.6.1

- <td>
+ <td width="107">
 Table 36

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 suffix "::type" is missing from the some of
 the examples.

- <td>
+ <td width="535">
 Change:
 Example:remove_const<const volatile int>::type
 evaluates to volatile int, whereas remove_const<const
@@ -12691,23 +12718,23 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 37

 <td>
 20.5.7

- <td>
+ <td width="107">
 Table 41

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 
 Typo.

@@ -12737,31 +12764,31 @@

 

- <td>
+ <td width="535">
 Add
 ”.”

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 70

 <td>
 20.6

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 Specifications now expressed via narrative text are more
 accurately and clearly expressed via executable code.

- <td>
+ <td width="535">
 Wherever
 concepts are available that directly match this
@@ -12773,46 +12800,46 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 71

 <td>
 20.6.7

- <td>
+ <td width="107">
 Table 51, last row, column 3

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 The grammar is incorrect.

- <td>
+ <td width="535">
 Change “conversion are” to “conversion
 is”.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 38

 <td>
 20.6.12.1.3

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 
 add the move requirement for bind's return type. 
@@ -12846,7 +12873,7 @@
 
 

- <td>
+ <td width="535">
 Add
 the following requirements. 
 "it has a public move constructor
@@ -12855,27 +12882,27 @@
 Add
 the MoveConstructible.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 39

 <td>
 20.6.16.2

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 
 There are no requires corresponding to F of std::function.

- <td>
+ <td width="535">
 
 Correct as follows.

@@ -12926,29 +12953,29 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 40

 <td>
 20.6.16.2

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 
 Thougn it's "Allocator Aloc" at other places, it's
 "Allocator A" only std::function constructor template
 parameter.

- <td>
+ <td width="535">
 
 Correct as follows.

@@ -12982,28 +13009,28 @@
 
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 41

 <td>
 20.6.16.2

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 
 There are no requires corresponding to R and Args of
 UsesAllocator.

- <td>
+ <td width="535">
 
 Correct as follows.

@@ -13041,23 +13068,23 @@

 }

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 42

 <td>
 20.6.16.2

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 The requires
 are wrong.
@@ -13067,7 +13094,7 @@
 by a definition of function, then it's a mistake to
 designate followings by MoveConstructible.

- <td>
+ <td width="535">
 
 Correct as follows.

@@ -13167,55 +13194,55 @@
 
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 208

 <td>
 20.6.17

- <td>
+ <td width="107">
 1

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 std::hash should
 be implemented for much more of the standard library. In
 particular for pair, tuple and all the standard containers.

 

- <td>
+ <td width="535">
 .

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 209

 <td>
 20.7

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 Smart pointers cannot be used in
 constrained templates

- <td>
+ <td width="535">
 Provide
 constraints for smart pointers

@@ -13223,24 +13250,24 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 213

 <td>
 20.7.6

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 std::allocator
 should be constrained to simplify its use on constrained
 contexts. This library component models allocation from
@@ -13252,62 +13279,62 @@

 

- <td>
+ <td width="535">
 The primary allocator template should be
 constrained to require ObjectType<T> and
 FreeStoreAllocatable<T>. Further operations to be
 constrained as required.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 214

 <td>
 20.7.8

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 
 raw_storage_iterator needs constraining as an iterator
 adaptor to be safely used in constrained templates

 

- <td>
+ <td width="535">
 Constrain the raw_storage_iterator template

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 210

 <td>
 20.7.11

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 Specialized algorithms for memory
 managenment need requirements to be easily usable in
 constrained templates

- <td>
+ <td width="535">
 Provide
 constraints for all algorithms in 20.7.11

@@ -13315,103 +13342,103 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 DE-20

 <td>
 20.7.12

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 DE-20 The section heading and the first sentence use the
 term "template function", which is undefined.

- <td>
+ <td width="535">
 Replace
 "template function" by "function template".

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 72

 <td>
 20.7.12

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 
 bind should support move-only functors and bound arguments.

 

- <td>
+ <td width="535">
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 DE-21

 <td>
 20.7.12.1.3

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 DE-21 The specification for bind claims twice that "the
 values and types for the bound arguments v1, v2, ..., vN
 are determined as specified below". No such specification
 appears to exist.

- <td>
+ <td width="535">
 Add the missing specification in the same section, or
 add a cross-reference indicating the section where the
 specification appears.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 211

 <td>
 20.7.12.2.3

- <td>
+ <td width="107">
 11

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 The nullptr_t
 type was introduced to resolve the null pointer literal
 problem. It should be used for the assignemnt operator, as
@@ -13419,29 +13446,29 @@

 

- <td>
+ <td width="535">
 Change signature here and in the synopsis
 to: unique_ptr& operator=(nullptr_t); Strike the
 sentance an note before the Effects clause.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 212

 <td>
 20.7.13.7

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 The
 pointer-safety API is nothing to do with smart pointers, so
 does not belong in 20.7.13. In fact it is a set of language
@@ -13451,55 +13478,55 @@

 

- <td>
+ <td width="535">
 Move this specification to 18.5. Move the
 declarations into the header <new>.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 DE-22

 <td>
 20.7.16.2

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 DE-22 The conditions for deriving from
 std::unary_function and std::binary_function are unclear:
 The condition would also be satisfied if ArgTypes were
 std::vector<T1>, because it (arguably) "contains" T1.

- <td>
+ <td width="535">
 Consider stating the conditions in normative prose
 instead of in comments in the class definition. Use
 "consists of" instead of "contains". Consider using "if and
 only if" instead of "iff".

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 73

 <td>
 20.7.18

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 The
 std::reference_closure template is redundant with
 std::function and should be removed.
@@ -13532,7 +13559,7 @@

 

- <td>
+ <td width="535">
 Remove 20.7.18
 [func.referenceclosure].

@@ -13540,23 +13567,23 @@

 Remove 5.1.1 paragraph 12.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 74

 <td>
 20.8

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 Scoped
 allocators represent a poor trade-off for standardization,
 since (1) scoped-allocator--aware containers can be
@@ -13584,7 +13611,7 @@

 

- <td>
+ <td width="535">
 Remove support
 for scoped allocators from the working paper. This includes
 at least the following changes:
@@ -13614,79 +13641,79 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 74

 <td>
 20.8.2.2

- <td>
+ <td width="107">
 (a) synopsis (b) after ¶ 14

- <td>
+ <td width="38">
 te/ed

- <td>
+ <td width="510">
 A concept name is twice misspelled.

- <td>
+ <td width="535">
 Change “Hasconstructor” to
 “HasConstructor” (twice).

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 75

 <td>
 20.8.2.2

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 Allocator concepts are incomplete

- <td>
+ <td width="535">
 See paper:
 http://www.halpernwightsoftware.com/WG21/n2810_allocator_defects.pdf

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 43

 <td>
 20.8.3

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 
 Typo.

 
 "alloc" should be "Alloc"

- <td>
+ <td width="535">
 
 Correct as follows.

@@ -13726,50 +13753,50 @@
 
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 215

 <td>
 20.8.3.3

- <td>
+ <td width="107">
 6,8

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 Extra pair of
 {}, presumably some formatting code gone awry :
 duration& operator-{-}();

 

- <td>
+ <td width="535">
 Remove the {} or fix formatting

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 77

 <td>
 20.8.4

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 
 Allocator-specific move and copy behavior for containers
 (N2525) complicates a little-used and already-complicated
@@ -13793,7 +13820,7 @@

 

- <td>
+ <td width="535">
 Remove 20.8.4.

 
@@ -13805,29 +13832,30 @@
 Remove all references to the facilities in
 20.8.4 and 20.8.5 from clause 23.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 78

 <td>
- 20.8.12, 20.8.13.2
+ 20.8.12, 
+ 20.8.13.2

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 There is presently no way to
 convert directly from a <code>shared_ptr</code> to a
 <code>unique_ptr</code>.

- <td>
+ <td width="535">
 Add
 an interface that performs the conversion. See the
 attached, Issues with the C++ Standard" paper under Chapter
@@ -13837,23 +13865,23 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 79

 <td>
 20.8.12.2.1

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 
 [unique.ptr.single.ctor]/5 no longer requires for D not to
 be a pointer type.  This restriction needs to be put
@@ -13876,26 +13904,26 @@

 

- <td>
+ <td width="535">
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 44

 <td>
 20.8.13.6

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 The
 1st parameter p and 2nd parameter v is now
 shared_ptr<T> *.
@@ -13905,28 +13933,28 @@
 shared_ptr<T>* then add the "p shall not be a null
 pointer" at the requires.

- <td>
+ <td width="535">
 
 Change shared_ptr<T>& or add the "p shall not be
 a null pionter" at the requires.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 45

 <td>
 20.9

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 
 Rep, Period, Clock and Duration don't correspond to
 concept.
@@ -13943,32 +13971,32 @@
 
 

- <td>
+ <td width="535">
 
 Make concept for Rep, Period, Clock and Duration, and fix
 20.9 and wait_until and wait_for's template parameter at
 30.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 80

 <td>
 20.9.2.1

- <td>
+ <td width="107">
 Heading

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 The section heading does not describe the contents.

- <td>
+ <td width="535">
 Change the
 heading “

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 81

 <td>
 20.9.3

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 
 chrono::duration is missing the modulous operator for both
 member and non-member arithmetic. This operator is useful
@@ -14036,7 +14064,7 @@

 

- <td>
+ <td width="535">
 Add:

 
@@ -14096,75 +14124,75 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 82

 <td>
 20.9.5.3

- <td>
+ <td width="107">
 after ¶ 1

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 The code synopsis has a minor alignment error.

- <td>
+ <td width="535">
 Align “rep” with the other symbols defined
 in this synopsis.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 216

 <td>
 21

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 All the containers use concepts for their
 iterator usage, exect for basic_string. This needs fixing.

- <td>
+ <td width="535">
 Use concepts for iterator template
 parameters throughout the chapter.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 46

 <td>
 21.2, 21.3

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 The
 basic_string does not use concept.

- <td>
+ <td width="535">
 The
 "class Alloc" is changed to "Allocator Alloc".

@@ -15158,23 +15186,23 @@
 
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 47

 <td>
 21.3

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 
 Typo. Missing ”>”

@@ -15195,27 +15223,27 @@

 

- <td>
+ <td width="535">
 
 Correct typo.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 48

 <td>
 21.3

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 
 char_traits does not use concept.

@@ -15239,33 +15267,33 @@
 
 

- <td>
+ <td width="535">
 Add
 a concept for char_traits.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 217

 <td>
 21.3

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 basic_string refers to
 constructible_with_allocator_suffix, which I thought was
 removed?

- <td>
+ <td width="535">
 Remove the
 lines: template <class charT, class traits, class Alloc
 struct constructible_with_allocator_suffix<
@@ -15274,24 +15302,24 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 218

 <td>
 21.3.1

- <td>
+ <td width="107">
 3

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 The identity
 "&*(s.begin() + n) == &*s.begin() + n" relies on
 operator& doing the "right thing", which (AFAICS) there
@@ -15302,53 +15330,54 @@

 

- <td>
+ <td width="535">
 See my recommendations for "23.2.1,
 23.2.6".

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 219

 <td>
- 21.3.6.6 [string.replace]
+ 21.3.6.6 
+ [string.replace]

- <td>
+ <td width="107">
 11

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 Effects refers to "whose first begin() - i1
 elements" However i1 is greater than begin()...

- <td>
+ <td width="535">
 Effects refers to "whose first i1 - begin()
 elements"

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 220

 <td>
 21.3.8.9

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 The
 operator<< for basic_string takes the output stream
 by r-value reference. This is different from the same
@@ -15358,29 +15387,29 @@

 

- <td>
+ <td width="535">
 Use the same reference type for the all the
 library types. This should be the r-value reference. There
 are other places in the standard where TR1, and new
 classes, did not receive an 'R-value' update.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 FR 33

 <td>
 22.1.1 [locale]

- <td>
+ <td width="107">
 3

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 ios_base::iostate err = 0;

 
@@ -15390,26 +15419,26 @@

 goodbit is the solution.

- <td>
+ <td width="535">
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 49

 <td>
 22.1.3.2.2

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 
 codecvt does not use concept. For example, create
 CodeConvert concept and change as follows.
@@ -15418,32 +15447,32 @@
 template<CodeConvert Codecvt, class Elem =
 wchar_t> class wstring_convert {

- <td>
+ <td width="535">
 Add
 a concept for codecvt.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 50

 <td>
 22.1.3.2.2

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 Add
 custom allocator parameter to wstring_convert, since we
 cannot allocate memory for strings from a custom allocator.

- <td>
+ <td width="535">
 
 Correct as follows.

@@ -15497,11 +15526,11 @@
 
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 FI 4

 <td>
@@ -15510,36 +15539,36 @@

 22.2.1.4.2

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 <tt>to_end and to_limit are both used. Only one is
 needed.</tt>

- <td>
+ <td width="535">
 Change to_limit to to_end.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 FI 5

 <td>
 <tt>22.2.1.4.2</tt>

- <td>
+ <td width="107">
 #3

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 <tt>[ Note: As
 a result of operations on state, it can return ok or
@@ -15566,33 +15595,34 @@
 from_next is unaltered, to_next is advanced, state is
 altered and return value is partial.</tt>

- <td>
+ <td width="535">
 <tt>[ Note: As a result of operations on state, do_in
 and do_out can return</tt> 
 <tt>ok or partial and set from_next == from and/or to_next
 != to. —end</tt> 
 <tt>note ]</tt>

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 FI 6

 <td>
 22.2.1.5

- See also 22.2.1.4 (1,2,3)
+ See also 
+ 22.2.1.4 (1,2,3)

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 
 <tt>codecvt_byname is only specified to work with locale
@@ -15610,27 +15640,27 @@

 

- <td>
+ <td width="535">
 <tt>There should be a built-in means to find a codecvt
 with a pair of character set names.</tt>

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 FI 7

 <td>
 22.2.1.4

- <td>
+ <td width="107">
 1,2,3

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 The word
 "codeset" is used, whereas the word "character set" is used
@@ -15640,28 +15670,28 @@

 

- <td>
+ <td width="535">
 Change "codeset" to "character set."

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 51

 <td>
 22.2.5.1.1

- <td>
+ <td width="107">
 7th para, 1st
 line

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 A
 parameter `end’ should be `fmtend’. 
 get() function had two `end’ parameters at N2321.
@@ -15679,7 +15709,7 @@
 
 

- <td>
+ <td width="535">
 
 Correct as follows.

@@ -15699,27 +15729,29 @@
 
 Requires: [fmt,fmtend) shall be a valid range.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 52

 <td>
- 22.2.5.1, 22.2.5.2, 22.2.6.1
+ 22.2.5.1, 
+ 22.2.5.2, 
+ 22.2.6.1

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 
 InputIterator does not use concept.

- <td>
+ <td width="535">
 
 Correct as follows.

@@ -15888,27 +15920,28 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 53

 <td>
- 22.2.5.3 , 22.2.5.4
+ 22.2.5.3 , 
+ 22.2.5.4

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 
 OutputIterator does not use concept.

- <td>
+ <td width="535">
 
 Correct as follows.

@@ -16021,57 +16054,57 @@
 typedef OutputIter
 iter_type;

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 54

 <td>
 23

- <td>
+ <td width="107">
 
 2nd para, Table 79

 

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 
 There is not <forward_list> in Table 79.

- <td>
+ <td width="535">
 Add
 <forward_list> between <deque> and
 <list>.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 221

 <td>
 23

- <td>
+ <td width="107">
 Table 79

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 The table is missing the new
 <forward_list> header.

- <td>
+ <td width="535">
 Add
 <forward_list> to the table for sequence containers.
 Alternative (technical) solution might be to merge
@@ -16079,24 +16112,24 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 222

 <td>
 23

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 It is not clear
 what purpose the Requirement tables serve in the Containers
 clause. Are they the definition of a library Container? Or
@@ -16113,7 +16146,7 @@

 

- <td>
+ <td width="535">
 Clarify all the tables in 23.1 are there as
 a convenience for documentation, rather than a strict set
 of requirements. Containers should be allowed to relax
@@ -16124,55 +16157,55 @@
 not provide the required size operation as it cannot be
 implemented efficiently.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 55

 <td>
 23.1.1

- <td>
+ <td width="107">
 
 3rd para, 4th line

 

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 It
 seems that “the MinimalAllocator concep” is the
 typo of “the MinimalAllocator concept”.

- <td>
+ <td width="535">
 
 Change to … models the MinimalAllocator
 concept.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 223

 <td>
 23.1.1

- <td>
+ <td width="107">
 3

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 The library does
 not define the MinimalAllocator or ScopedAllocator
 concepts, these were part of an earlier Allocators proposal
@@ -16180,34 +16213,34 @@

 

- <td>
+ <td width="535">
 Remove the references to MinimalAllocator
 and ScopedAllocator, or add definitions for these concepts
 to clause 20.7.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 224

 <td>
 23.1.1

- <td>
+ <td width="107">
 8

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 This paragraph implicitly requires all
 containers in clause 23 to support allocators, which
 std::array does not.

- <td>
+ <td width="535">
 Add an 'unless
 otherwise specified' rider somewhere in p8, or move the
 whole array container from clause 23 [containers] to clause
@@ -16215,24 +16248,24 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 225

 <td>
 23.1.1

- <td>
+ <td width="107">
 Table 81

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 Inconsistent
 words used to say the same thing. Table 80 describes
 iterator/const_iterator typedef as returning an "iterator
@@ -16243,29 +16276,29 @@

 

- <td>
+ <td width="535">
 Change return types for
 X::(const)_reverse_iterator to say "iterator type whose
 value type is (const) T".

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 226

 <td>
 23.1.1

- <td>
+ <td width="107">
 10

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 <array>
 must be added to this list. In particular it doesn't
 satisfy: - no swap() function invalidates any references,
@@ -16275,90 +16308,90 @@

 

- <td>
+ <td width="535">
 If <array> remains a container, this
 will have to also reference array, which will then have to
 say which of these points it satisfies.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 227

 <td>
 23.1.1

- <td>
+ <td width="107">
 Table 80

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 The post-condition for a = rv uses the word
 “construction” when it means
 “assignment”

- <td>
+ <td width="535">
 Replace the word
 “construction” with the word
 “assignment”

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 228

 <td>
 23.1.1

- <td>
+ <td width="107">
 3

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 Line 4 contains
 a spelling mistake in the fragment "MinimalAllocator
 concep."

 

- <td>
+ <td width="535">
 Replace "concep" with "concept"

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 229

 <td>
 23.1.1

- <td>
+ <td width="107">
 3

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 The fragment "A container may directly call
 constructors" is not technically correct as constructors
 are not callable.

- <td>
+ <td width="535">
 Replace "A
 container may directly call constructors and destructors
 for its stored objects" with something similar to "A
@@ -16367,24 +16400,24 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 230

 <td>
 23.1.2

- <td>
+ <td width="107">
 1

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 
 “implementations shall consider the following
 functions to be const” - what does this mean? I don't
@@ -16394,33 +16427,33 @@

 

- <td>
+ <td width="535">
 Clarify what is meant and what requirements
 an implementation must satisfy.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 56

 <td>
 23.1.3

- <td>
+ <td width="107">
 12th para, Table 84

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 
 `array’ is unstated in Table 84 - Optional sequence
 container operations.

- <td>
+ <td width="535">
 Add
 `array’ to Container field for the following
 Expression.
@@ -16437,84 +16470,84 @@
 a.at(n)

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 231

 <td>
 23.1.3

- <td>
+ <td width="107">
 9-11

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 These paragraphs
 are redundant now that Concepts define what it means to be
 an Iterator and guide overload resolution accordingly.

 

- <td>
+ <td width="535">
 Strike 23.1.3p9-11. Make sure
 std::basic_string has constraints similar to std::vector to
 meet this old guarantee.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 232

 <td>
 23.1.3

- <td>
+ <td width="107">
 Table 84

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 match_results
 may follow the requirements but is not listed a general
 purpose library container.

 

- <td>
+ <td width="535">
 Remove reference to match_results against
 a[n] operation

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 233

 <td>
 23.1.3

- <td>
+ <td width="107">
 Table 84

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 Add references to the new containers.

- <td>
+ <td width="535">
 Add reference to
 array to the rows for: a.front(), a. back(), a[n] a.at(n).
 Add reference to forward_list to the rows for: a.front(),
@@ -16524,24 +16557,24 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 234

 <td>
 23.1.3

- <td>
+ <td width="107">
 Table 84

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 Ther reference
 to iterator in semantics for back should also allow for
 const_iterator when called on a const-qualified container.
@@ -16550,34 +16583,34 @@

 

- <td>
+ <td width="535">
 Replace iterator with auto in semantics for
 back: { auto tmp = a.end(); --tmp; return *tmp; }

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 235

 <td>
 23.1.3

- <td>
+ <td width="107">
 1

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 “The library provides three basic
 kinds of sequence containers: vector, list, and
 deque” - text appears to be out of date re addition
 of array and forward_list

- <td>
+ <td width="535">
 Change the text
 to read: “The library provides five basic kinds of
 sequence containers: array, deque, forward_list, list and
@@ -16585,24 +16618,24 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 236

 <td>
 23.1.3

- <td>
+ <td width="107">
 2

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 [ I've moved (1)
 into a separate comment because I believe it is editorial
 in the simple sense, whereas (2) and (3) are not so
@@ -16619,32 +16652,32 @@

 

- <td>
+ <td width="535">
 Remove this paragraph

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 237

 <td>
 23.1.3

- <td>
+ <td width="107">
 2

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 vector, list, and deque offer the
 programmer different complexity trade-offs and should be
 used accordingly - this ignores array and forward_list

- <td>
+ <td width="535">
 Modify the text
 to read: "array, deque, forward_list, list and vector offer
 the programmer different complexity trade-offs and should
@@ -16652,24 +16685,24 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 238

 <td>
 23.1.4

- <td>
+ <td width="107">
 6

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 Leaving it
 unspecified whether or not iterator and const_iterator are
 the same type is dangerous, as user code may or may not
@@ -16682,7 +16715,7 @@

 

- <td>
+ <td width="535">
 Change 'unspecified' to 'implementation
 defined'. Add "[Note: As itererator and const_iterator have
 identical semantics in this case, and iterator is
@@ -16690,29 +16723,29 @@
 the One Definition Rule by always using const_iterator in
 their function parameter lists -- end note]

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 239

 <td>
 23.1.4

- <td>
+ <td width="107">
 85

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 It is not possible to take a move-only key
 out of an unordered container, such as (multi)set or
 (multi)map, or the new hashed containers.

- <td>
+ <td width="535">
 Add below
 a.erase(q), a.extract(q), with the following notation:
 a.extract(q), Return type pair<key, iterator>
@@ -16724,24 +16757,24 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 240

 <td>
 23.1.6.1

- <td>
+ <td width="107">
 12

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 The axiom
 EmplacePushEquivalence should be asserting the stronger
 contract that emplace and insert return the same iterator
@@ -16756,7 +16789,7 @@

 

- <td>
+ <td width="535">
 Remove the * to deference the returned
 iterator either side of the == in the
 EmplacePushEquivalence axiom, rename the axiom
@@ -16767,110 +16800,110 @@
 position, Args... args) { emplace(c, position, args...) ==
 insert(c, position, value_type(args...)); }

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 57

 <td>
 23.1.6.3

- <td>
+ <td width="107">
 
 1st para, 4th line

 

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 
 Typo, duplicated "to"

 
 "to to model insertion container concepts."

- <td>
+ <td width="535">
 
 Remove one.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 241

 <td>
 23.2.1

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 std::array does
 not have an allocator, so need to document an exception to
 the requirements of 23.1.1p3

 

- <td>
+ <td width="535">
 add exception to 23.1.1p3

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 242

 <td>
 23.2.1

- <td>
+ <td width="107">
 3

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 std:: qualification no longer needed for
 reverse_iterator.

- <td>
+ <td width="535">
 remove std::
 qualification from std::reverse_iterator<iterator>
 and std::reverse_iterator<const_iterator>

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 243

 <td>
 23.2.1

- <td>
+ <td width="107">
 3

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 Most containers,
 and types in general have 3 swaps: swap(T&, T&)
 swap(T&&, T&) swap(T&, T&&) But
@@ -16878,27 +16911,27 @@

 

- <td>
+ <td width="535">
 add the other two swaps.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 244

 <td>
 23.2.1, 23.2.6

- <td>
+ <td width="107">
 1

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 The validity of
 the expression &a[n] == &a[0] + n is contingent on
 operator& doing the “right thing” (as
@@ -16911,7 +16944,7 @@

 

- <td>
+ <td width="535">
 Define a ContiguousStrorage and apply it to
 vector,array and string. The Concept (supplied by Alisdair
 M) looks like this: Concept< typename C >
@@ -16920,24 +16953,24 @@
 Contiguous { C c; true = equal_ranges( data( c), data(c) +
 size(c), begin(c)); } };

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 245

 <td>
 23.2.3

- <td>
+ <td width="107">
 2

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 The predicate types used in special member
 function of forward_list should be CopyConstructible, as
 per the algorithms of the same name. Note: an alternate
@@ -16946,7 +16979,7 @@
 library specification in general. See earlier comment for
 details, that would render this one redundant.

- <td>
+ <td width="535">
 Add
 CopyConstructible requirement to the following signatures:
 template <Predicate<auto, T> Pred> requires
@@ -16966,59 +16999,59 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 58

 <td>
 23.2.3.2

- <td>
+ <td width="107">
 
 1st line
 before 1st para

 

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 
 Unnecessary "{" exists before a word iterator like
 "{iterator before_begin()".

- <td>
+ <td width="535">
 
 Remove "{"

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 59

 <td>
 23.2.4.4

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 
 Types of the third and forth parameter of splice() are
 iterator at 23.2.4.4, though types of them are
 const_iterator at 23.2.4. (They are both const_iterator on
 N2350)

- <td>
+ <td width="535">
 
 Correct as follows.

@@ -17057,23 +17090,23 @@
 
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 83

 <td>
 23.2.6.2

- <td>
+ <td width="107">
 7

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 
 "shrink_to_fint" should be "shrink_to_fit".

@@ -17082,27 +17115,27 @@

 

- <td>
+ <td width="535">
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 246

 <td>
 23.3.2.2

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 The content of
 this sub-clause is purely trying to describe in words the
 effect of the requires clauses on these operations, now
@@ -17113,29 +17146,29 @@

 

- <td>
+ <td width="535">
 Strike 23.3.2.2 entirely. (but do NOT
 strike these signatures from the class template
 definition!)

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 247

 <td>
 24.1

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Ge

- <td>
+ <td width="510">
 Iterator
 concepts are not extensive enough to merit a whole new
 header, and should be merged into <concpts>. This is
@@ -17147,30 +17180,30 @@

 

- <td>
+ <td width="535">
 Move the concepts of
 <iterator_concepts> into the <concepts> header.
 We take no position on moving the text from Clause 24 to
 Clause 20 though.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 248

 <td>
 24.1

- <td>
+ <td width="107">
 6

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 The text "so for
 any iterator type there is an iterator value that points
 past the last element of a corresponding container" is
@@ -17180,55 +17213,55 @@

 

- <td>
+ <td width="535">
 Replace the reference to container with a
 more appropriate concept

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 250

 <td>
 24.1.1

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 A default implementation should be supplied
 for the post-increment operator to simplify implementation
 of iterators by users.

- <td>
+ <td width="535">
 Copy the Effects clause into the concept
 description as the default implementation. Assumes a
 default value for postincrement_result

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 251

 <td>
 24.1.1

- <td>
+ <td width="107">
 3

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 The
 post-increment operator is dangerous for a general
 InputIterator. The multi-pass guarantees that make it
@@ -17242,16 +17275,16 @@

 

- <td>
+ <td width="535">
 Move declaration of postincrement operator
 and postincrement_result type from Interator concept to the
 ForwardIterator concept

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 252
@@ -17261,38 +17294,38 @@
 <td>
 24.1.2

- <td>
+ <td width="107">
 3

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 istream_iterator is not a class, but a
 class template

- <td>
+ <td width="535">
 Change 'class' to 'class template' in the
 note.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 253

 <td>
 24.1.3

- <td>
+ <td width="107">
 1

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 First sentance
 does not make gramatical sense, Seems to be missing the
 words 'if it' by comparison with similar sentance in other
@@ -17300,113 +17333,113 @@

 

- <td>
+ <td width="535">
 Add the words 'if it' : "X satisfies the
 requirements of an output iterator IF IT meets the
 syntactic and semantic requirements"

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 254

 <td>
 24.1.3

- <td>
+ <td width="107">
 5

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 This
 postcondition for pre-increment operator should be written
 as an axiom

 

- <td>
+ <td width="535">
 Move the postcondition into the concept
 definition as an axiom

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 255

 <td>
 24.1.4

- <td>
+ <td width="107">
 4

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 This
 postcondition for pre-increment operator should be written
 as an axiom

 

- <td>
+ <td width="535">
 Move the postcondition into the concept
 definition as an axiom

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 256

 <td>
 24.1.5

- <td>
+ <td width="107">
 3, 4, 5

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 The relationship between pre- and post-
 decrement should be expressed as an axiom.

- <td>
+ <td width="535">
 Move the text
 specification of pre/post-conditions and behaviour into an
 axiom within the BidirectionalIterator concept

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 257

 <td>
 24.1.5

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 There is a
 reasonable default for postdecrement_result type, which is
 X. X is required to be regular, therefore CopyConstructible
@@ -17415,57 +17448,57 @@

 

- <td>
+ <td width="535">
 Add the default : typename
 postincrement_result = X;

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 258

 <td>
 24.1.5

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 A default
 implementation should be supplied for the post-decrement
 operator to simplify implementation of iterators by users.

 

- <td>
+ <td width="535">
 Copy the Effects clause into the concept
 description as the default implementation. Assumes a
 default value for postincrement_result

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 259

 <td>
 24.1.5

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 
 postdecrement_result is effectively returning a copy of the
 original iterator value, so should have similar
@@ -17475,34 +17508,34 @@

 

- <td>
+ <td width="535">
 Add the requirement: requires Iterator<
 postdecrement_result >;

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 260

 <td>
 24.1.5

- <td>
+ <td width="107">
 6

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 The effects clause for post-decrement
 iterator should be available as an axiom and a default
 implementation, where the compiler can make better use of
 it.

- <td>
+ <td width="535">
 Move the Effects
 clause into the BidirectionalIterator concept definition as
 an axiom, and as the default implementation for the
@@ -17510,11 +17543,11 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 249

@@ -17522,13 +17555,13 @@
 24.1.6

- <td>
+ <td width="107">
 2

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 The semantic for
 operator+= should also be provided as a default
 implementation to simplify implementation of user-defined
@@ -17536,61 +17569,61 @@

 

- <td>
+ <td width="535">
 Copy the text from the effects clause into
 the RandomAccessIterator concept as the default
 implementaiton.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 261

 <td>
 24.1.6

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 To simplify user
 defined random access iterator types, the
 subscript_reference type should default to reference

 

- <td>
+ <td width="535">
 typename subscript_reference = reference;

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 262

 <td>
 24.1.6

- <td>
+ <td width="107">
 3, 4

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 Effects and post-conditions for operator+
 are more useful if expressed as axioms, and supplied as
 default implementations.

- <td>
+ <td width="535">
 Move the effects
 and Postcondition definitions into the RandomAccessIterator
 concept and copy the code in the specification as the
@@ -17598,29 +17631,29 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 263

 <td>
 24.1.6

- <td>
+ <td width="107">
 5

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 This requirement on operator-= would be
 better expressed as a default implementation in the
 concept, with a matching axiom

- <td>
+ <td width="535">
 Move the
 specification for operator-= from the returns clause into
 an axiom and default implementation within the
@@ -17628,52 +17661,52 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 264

 <td>
 24.1.6

- <td>
+ <td width="107">
 6

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 Effects clauses are better expressed as
 axioms where possible.

- <td>
+ <td width="535">
 Move code in
 operator- effects clause into RandomAccessIterator concept
 as both a default implementation and an axiom

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 265

 <td>
 24.1.6

- <td>
+ <td width="107">
 8

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 This effects
 clause is nonesense. It looks more like an axiom stating
 equivalence, and certainly an effects clause cannot change
@@ -17681,31 +17714,31 @@

 

- <td>
+ <td width="535">
 Strike the Effects clause

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 266

 <td>
 24.1.6

- <td>
+ <td width="107">
 9

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 This sentance should be provided as a
 default definition, along with a matching axiom

- <td>
+ <td width="535">
 Move the Returns
 clause into the spefication for RandomAccessIterator
 operator- as a default implementation. Move the Effects
@@ -17713,52 +17746,52 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 267

 <td>
 24.1.6

- <td>
+ <td width="107">
 24.1.6

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 The code in the
 Requires clause for RandomAccessIterator operator[] would
 be better expressed as an axiom.

 

- <td>
+ <td width="535">
 Rewrite the Requires clause as an axiom in
 the RandomAccessIterator concept

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 268

 <td>
 24.1.6

- <td>
+ <td width="107">
 12

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 This note is
 potentialy confusing as __far enters the syntax as a clear
 language extension, but the note treats it as a regular
@@ -17767,29 +17800,29 @@

 

- <td>
+ <td width="535">
 Clean up the note to either avoid using
 language extension, or spell out this is a constraint to
 support extensions.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 60

 <td>
 24.1.8

- <td>
+ <td width="107">
 1st para

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 
 Capability of an iterator is too much restricted by
 concept.
@@ -17961,85 +17994,85 @@
 
 

- <td>
+ <td width="535">
 Add
 InputRange, OutputRange, ForwardRange, BidirectionalRange
 and RandomAccessRange.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 269

 <td>
 24.3

- <td>
+ <td width="107">
 3

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 'decrements for
 negative n' seems to imply a negative number of decrement
 operations, which is odd.

 

- <td>
+ <td width="535">
 Need simple, clearer wording

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 270

 <td>
 24.3

- <td>
+ <td width="107">
 4

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 The reachability
 constraint in p5 means that a negavite result, implying
 decrements operations in p4, is not possible

 

- <td>
+ <td width="535">
 Split the two overloads into separate
 descriptions, where reachability is permitted to be in
 either direction for RandomAccessIterator

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 271

 <td>
 24.3

- <td>
+ <td width="107">
 6,7

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 next/prev return
 an incremented iterator without changing the value of the
 original iterator. However, even this may invalidate an
@@ -18048,28 +18081,28 @@

 

- <td>
+ <td width="535">
 Replace InputIterator constraint with
 FOrwardIterator in next and prev function templates.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 272

 <td>
 24.4

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 reverse_iterator
 and move_iterator use different formulations for their
 comparison operations. move_iterator merely requires the
@@ -18088,29 +18121,29 @@

 

- <td>
+ <td width="535">
 Rephrase the reverse_iterator comparison
 operations using only operators < and ==, as per the
 move_iterator specification.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 274

 <td>
 24.4, 24.5

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 The subclauses
 for standard iterator adaptors could be better organised.
 There are essentially 3 kinds of iterator wrappers
@@ -18123,30 +18156,30 @@

 

- <td>
+ <td width="535">
 Promote 24.4.2 [insert.iterators] up one
 level to 24.6. Emphasize that insert iterators adapt
 containers Retarget 24.4 [predef.iterators] as iterator
 adapters for iterator templates that wrap other iterators.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 275

 <td>
 24.4.1.1

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 The constructor
 template taking a single Iterator argument will be selected
 for Copy Initialization instead of the non-template
@@ -18155,28 +18188,28 @@

 

- <td>
+ <td width="535">
 The reverse_iterator template constructor
 taking a single Iterator argument should be explicit.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 276

 <td>
 24.4.1.1

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 It is odd to
 have a mix of declaration stlyes for operator+ overloads.
 Prefer if either all are member functions, or all are
@@ -18184,28 +18217,28 @@

 

- <td>
+ <td width="535">
 Make the member operators taking a
 difference_type argument non-member operators

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 277

 <td>
 24.4.1.2.1

- <td>
+ <td width="107">
 1

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 The default
 constructor default-initializes current, rather than
 value-initializes. This means that when Iterator
@@ -18218,7 +18251,7 @@

 

- <td>
+ <td width="535">
 i/ Specify value initialization rather than
 default intialization or ii/ specify = default; rather than
 spell out the semantic. This will at least allow users to
@@ -18226,24 +18259,24 @@
 iii/ Add a note to the description emphasizing the singular
 nature of a value-initialized reserve iterator.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 278

 <td>
 24.4.1.2.1

- <td>
+ <td width="107">
 3

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 There is an
 inconsistency between the constructor taking an iterator
 and the constructor template taking a reverse_iterator
@@ -18253,28 +18286,29 @@

 

- <td>
+ <td width="535">
 Change the const reverse_iterator
 & parameter to pass-by-value

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 279

 <td>
- 24.4.1.2.12, 24.4.3.2.12
+ 24.4.1.2.12, 
+ 24.4.3.2.12

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 The reason the
 return type became unspecified is LWG issue 386. This
 reasoning no longer applies as there are at least two ways
@@ -18283,28 +18317,28 @@

 

- <td>
+ <td width="535">
 Specify the return type using either
 decltype or the Iter concept map

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 280

 <td>
 24.4.1.2.4

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 The presence of
 the second iterator value is surprising for many readers
 who underestimate the size of a reverse_iterator object.
@@ -18313,28 +18347,28 @@

 

- <td>
+ <td width="535">
 Add reverse_iterator expsoition only member
 tmp as a comment to class declaration, as a private member

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 281

 <td>
 24.4.1.2.5

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 The current
 specification for return value will always be a true
 pointer type, but reverse_iterator supports proxy iterators
@@ -18342,57 +18376,62 @@

 

- <td>
+ <td width="535">
 Replace the existing returns specification
 with a copy of the operator* specification that returns
 this->tmp.operator->

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 282

 <td>
- 24.4.2.1, 24.4.2.2.2, 24.4.2.3,
- 24.4.2.4.2, 24.4.2.5, 24.4.2.6.2
+ 24.4.2.1, 
+ 24.4.2.2.2, 
+ 24.4.2.3, 
+ 24.4.2.4.2, 
+ 24.4.2.5, 
+ 24.4.2.6.2

- <td>
+ <td width="107">
 n/a

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 Insert iterators of move-only types will
 move from lvalues

- <td>
+ <td width="535">
 Add an additional constrained overload for
 operator= that requires
 !CopyConstructible<Cont::value_type> and mark it
 =delete.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 283

 <td>
- 24.4.2.5, 24.4.2.6.4
+ 24.4.2.5, 
+ 24.4.2.6.4

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 postincrement operator overloads
 traditionally return by value - insert_iterator is declared
 as return by reference. The change is harmless in this
@@ -18400,113 +18439,113 @@
 matching change for consistency, or this function should
 return-by-value

- <td>
+ <td width="535">
 change operator++(int) overload to return
 by value, not reference. Affects both class summary and
 operator definition in p

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 61

 <td>
 24.4.3.2.1

- <td>
+ <td width="107">
 2nd para, 1st
 line

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 
 Typo.

 
 "intializing" should be "initializing"

- <td>
+ <td width="535">
 Add
 "i"

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 284

 <td>
 24.5

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 The stream
 iterators need constraining with concepts/requrires
 clauses.

 

- <td>
+ <td width="535">
 Provide constraints

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 285

 <td>
 24.5.1

- <td>
+ <td width="107">
 1,2

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 Much of the
 content of p1 and the whole of p2 is a redundant
 redefinition of InputIterator. It should be simplified

 

- <td>
+ <td width="535">
 Strike p2. Simplify p1 and add a
 cross-reference to the definition of InputIterator concept.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 286

 <td>
 24.5.1

- <td>
+ <td width="107">
 3

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 To the casual
 reader it is not clear if it is intended to be able to
 assign to istream_iterator objects. Specifying the copy
@@ -18515,29 +18554,29 @@

 

- <td>
+ <td width="535">
 Either provide a similar definition to the
 copy-assign operator as for the copy constructor, or strike
 the copy constructor

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 287

 <td>
 24.5.1.1

- <td>
+ <td width="107">
 2

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 It is not clear
 what the intial state of an istream_iterator should be. Is
 _value_ initialized by reading the stream, or default/value
@@ -18549,57 +18588,57 @@

 

- <td>
+ <td width="535">
 Specify _value_ is initialized by reading
 the stream, or the iterator takes on the end-of-stream
 value if the stream is empty

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 288

 <td>
 24.5.1.1

- <td>
+ <td width="107">
 3

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 The provided specification is vacuous,
 offering no useful information.

- <td>
+ <td width="535">
 Either strike
 the specification of the copy constructor, or simply
 replace it with an = default definition.

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 289

 <td>
 24.5.1.2

- <td>
+ <td width="107">
 6

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 It is very hard
 to pick up the correct specification for
 istream_iterator::operator== as the complete specification
@@ -18611,29 +18650,29 @@

 

- <td>
+ <td width="535">
 Merge 24.5.1p3, equality comparison of
 end-of-stream-iterators, into 24.5.1.2p6, the specification
 of the equality operator for istream_iterator.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 290

 <td>
 24.5.2

- <td>
+ <td width="107">
 1

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 The character
 type of a string delimiter for an ostream_iterator should
 be const charT *, the type of the elements, not char *, a
@@ -18641,27 +18680,27 @@

 

- <td>
+ <td width="535">
 Replace char * with const charT *

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 291

 <td>
 24.5.2.2

- <td>
+ <td width="107">
 2

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 ostream_iterator
 postincrement operator returns by reference rather than by
 value. This may be a small efficiency gain, but it is
@@ -18669,86 +18708,87 @@

 

- <td>
+ <td width="535">
 ostream_iterator operator++(int);

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 FR 34

 <td>
- 24.5.3 [istreambuf.iterator]
+ 24.5.3 
+ [istreambuf.iterator]

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 There are two public
 sections, and the content of the second one is indented
 with respect to the first. I don't it should be.

 

- <td>
+ <td width="535">
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 292

 <td>
 24.5.3

- <td>
+ <td width="107">
 1

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 Prefer the use
 of the new nullptr constant to the zero literal when using
 a null pointer in text.

 

- <td>
+ <td width="535">
 Change istreambuf_iterator(0) to
 istreambuf_iterator(nullptr)

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 293

 <td>
 24.5.3

- <td>
+ <td width="107">
 2,3,4

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 The listed paragraphs redundantly redefine
 an input iterator, and redundancy can be a dangerous thing
 in a specification. Suggest a simpler phrasing below.

- <td>
+ <td width="535">
 2. The result of
 operator*() on an end of stream is undefined. For any other
 iterator value a char_type value is returned. 3. Two end of
@@ -18761,29 +18801,29 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 294

 <td>
 24.5.3.2

- <td>
+ <td width="107">
 2

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 Implicit converting constructors can be
 invoked at surprising times, so there should always be a
 good reason for declaring one.

- <td>
+ <td width="535">
 Mark the two
 single-argument constructors take a stream or stream buffer
 as explicit. The proxy constructor should remain implicit.
@@ -18795,24 +18835,24 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 295

 <td>
 25

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 THere is a level
 of redundancy in the library specification for many
 algorithms that can be eliminated with the combination of
@@ -18822,26 +18862,27 @@

 

- <td>
+ <td width="535">
 Adopt n2743, or an update of that paper.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 62

 <td>
- 25, 25.3.1.5, 26.3.6.5
+ 25, 25.3.1.5, 
+ 26.3.6.5

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 
 The return types of is_sorted_until function and
@@ -18857,31 +18898,31 @@
 

- <td>
+ <td width="535">
 
 Change "is_sorted_until" to "sorted_bound"

 
 Change "is_heap" to "heap_bound"

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 296

 <td>
 25.1.8

- <td>
+ <td width="107">
 1

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 The 'Returns' of
 adjacent_find requires only HasEqualTo, or a Predicate.
 Requiring EqualityComparable or EquivalenceRelation seems
@@ -18889,111 +18930,111 @@

 

- <td>
+ <td width="535">
 Change EqualityComparable to HasEqualTo and
 EquivalnceRelation to Predicate

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 297

 <td>
 25.2.11

- <td>
+ <td width="107">
 6

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 The definition
 of rotate_copy is very complicated. It is equivalent to:
 return copy(first, middle, copy(middle, last, result));

 

- <td>
+ <td width="535">
 Change 'effects' to, returns, requires,
 complexity to: effects: equivalent to: return copy(first,
 middle, copy(middle, last, result));

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 298

 <td>
 25.2.13

- <td>
+ <td width="107">
 13

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 partition_point requires a partitioned
 array

- <td>
+ <td width="535">
 requires: is_partitioned(first, last, pred)
 != false;

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 299

 <td>
 25.2.2

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 Should be consistent in style use of
 concepts in template parameter lists. The
 auto-OutputIterator sytle used in std::copy is probably
 preferred.

- <td>
+ <td width="535">
 Change way signature is declared:
 template<InputIterator InIter, OutputIterator<auto,
 RvalueOf<InIter::reference>::type> OutIter>
 OutIter move(InIter first, InIter last, OutIter result);

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 300

 <td>
 25.2.3

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 Since publishing
 the original standard, we have learned that swap is a
 fundamental operation, and several common idioms rely on it
@@ -19009,31 +19050,31 @@

 

- <td>
+ <td width="535">
 Move primary swap template from
 <algorithm> into <utility>. Move 25.2.3 to
 somewhere under 20.2. Require <algorithm> to #include
 <utility> to access pair and provide legacy support
 for finding swap.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 301

 <td>
 25.2.5

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 replace and
 replace_if have the requirement: OutputIterator<Iter,
 Iter::reference> Which implies they need to copy some
@@ -19044,161 +19085,162 @@

 

- <td>
+ <td width="535">
 Remove OutputIterator<Iter,
 Iter::reference> from replace and replace_if

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 302

 <td>
 25.3

- <td>
+ <td width="107">
 4

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 the concept
 StrictWeakOrder covers the definition of a strict weak
 ordering, described in paragraph 4.

 

- <td>
+ <td width="535">
 Remove 4, and mention StrictWeakOrder in
 paragraph 1.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 303

 <td>
 25.3

- <td>
+ <td width="107">
 6

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 This paragraph just describes
 is_partitioned

- <td>
+ <td width="535">
 6 A sequence
 [start,finish) is partitioned with respect to an expression
 f(e) if is_partitioned(start, finish, e) != false

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 304

 <td>
 25.3.6

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 The requires
 clauses of push_heap, pop_heap and make_heap are
 inconsistently formatted, dispite being identical

 

- <td>
+ <td width="535">
 Format them identically.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 305

 <td>
 25.3.7

- <td>
+ <td width="107">
 1, 9, 17

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 The negative requirement on IsSameType is a
 hold-over from an earlier draught with a variadic template
 form of min/max algorith. It is no longer necessary.

- <td>
+ <td width="535">
 Strike the !IsSameType<T, Compare>
 constraint on min/max/minmax algorithms

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 84

 <td>
 26

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 ge

- <td>
+ <td width="510">
 
 Parts of the numerics chapter are not concept enabled.

 

- <td>
+ <td width="535">
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 FR 35

 <td>
- 26.3 [Complex numbers]
+ 26.3 
+ [Complex numbers]

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 Instantiations of the class
 template complex<> have to be allowed for integral
 types, to reflect existing practice and ISO standards
@@ -19206,53 +19248,53 @@

 

- <td>
+ <td width="535">
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 306

 <td>
 26.4

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 Random number
 library component cannot be used in constrained templates

 

- <td>
+ <td width="535">
 Provide constraints for the random number
 library

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 63

 <td>
 26.4.8.5.1

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 No
 constructor of discrete_distribution that accepts
 initializer_list.
@@ -19283,30 +19325,30 @@
 
 

- <td>
+ <td width="535">
 Add
 the following constructer.

 
 discrete_distribution(initializer_list<result_type>);

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 64

 <td>
 26.5.2

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 
 “valarray<T>& operator+=
@@ -19315,29 +19357,29 @@
 
 

- <td>
+ <td width="535">
 Add
 valarray<T>& operator+=
 (initializer_list<T>);

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 307

 <td>
 26.7

- <td>
+ <td width="107">
 Footnote 288

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 The footnote
 refers to TR1, which is not a defined term in this
 standard. Drop the reference to TR1, those templates are a
@@ -19346,79 +19388,79 @@

 

- <td>
+ <td width="535">
 Drop the reference to TR1.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 85

 <td>
 27

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 ge

- <td>
+ <td width="510">
 The
 input/output chapter is not concept enabled.

 

- <td>
+ <td width="535">
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 308

 <td>
 27

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 
 iostreams library cannot be used from
 constrained templates

 

- <td>
+ <td width="535">
 Provide constraints for the iostreams
 library, clause 27

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 65

 <td>
 27.4.4

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 Switch from
 “unspecified-bool-type” to
 

- <td>
+ <td width="535">
 
 Replace "operator unspecified-bool-type() const;"
 with "explicit operator bool() const;"

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 66

 <td>
 27.4.4.3

- <td>
+ <td width="107">
 1st para

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 Switch from
 “unspecified-bool-type” to
 

- <td>
+ <td width="535">
 
 Replace "operator unspecified-bool-type() const;"
 with "explicit operator bool() const;"

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 FR 36

 <td>
- 27.6.1.2.2 [istream.formatted.arithmetic]
+ 27.6.1.2.2 [istream. 
+ formatted.arithmetic]

- <td>
+ <td width="107">
 1, 2, and 3

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 iostate err = 0;

 
@@ -19493,26 +19536,27 @@

 

- <td>
+ <td width="535">
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 FR 37

 <td>
- 27.6.1.2.2 [istream.formatted.arithmetic]
+ 27.6.1.2.2 [istream. 
+ formatted.arithmetic]

- <td>
+ <td width="107">
 3

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 else if (lval <
 numeric_limits<int>::min()

@@ -19526,30 +19570,30 @@

 

- <td>
+ <td width="535">
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 67

 <td>
 27.7.1

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 
 basic_stringbuf dose not use concept.

- <td>
+ <td width="535">
 
 Replace “class Allocator” to “Allocator
 Alloc”.
@@ -19675,27 +19719,27 @@
 
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 68

 <td>
 27.7.2

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 
 basic_istringstream dose not use concept.

- <td>
+ <td width="535">
 
 Replace “class Allocator” to “Allocator
 Alloc”.
@@ -19852,27 +19896,27 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 69

 <td>
 27.7.3

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 
 basic_ostringstream dose not use concept.

- <td>
+ <td width="535">
 
 Replace “class Allocator” to “Allocator
 Alloc”.
@@ -20030,30 +20074,30 @@
 
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 71

 <td>
 27.7.3

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 
 Typo.

 "template" is missing in
 "class basic_ostringstream" of the title of the chapter.

- <td>
+ <td width="535">
 
 Correct as follows.

@@ -20072,27 +20116,27 @@
 27.7.3 Class template
 basic_ostringstream

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 72

 <td>
 27.7.4

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 
 basic_stringstream dose not use concept.

- <td>
+ <td width="535">
 
 Replace "class Allocator" to "Allocator Alloc".

@@ -20244,23 +20288,23 @@

 }

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 73

 <td>
 27.8.1.14

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 It is a problem
 from C++98, fstream cannot appoint a filename of wide
@@ -20269,106 +20313,106 @@
 
 

- <td>
+ <td width="535">
 Add
 interface corresponding to wchar_t, char16_t and char32_t.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 86

 <td>
 28

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 ge

- <td>
+ <td width="510">
 The
 regular expressions chapter is not concept enabled.

 

- <td>
+ <td width="535">
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 309

 <td>
 28

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 Regular
 expressions cannot be used in constrained templates

 

- <td>
+ <td width="535">
 Provide constraints for the regular
 expression library, clause 28

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 310

 <td>
 28

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 The regex chapter uses iterators in the old
 pre-concept style, it should be changed to use concepts
 instead.

- <td>
+ <td width="535">
 Use concepts for iterator template
 arguments throughout.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 314

 <td>
 28.4

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 The swap
 overloads for regex classes are only supplied for l-value
 references. Other sections of the library (eg 21 strings or
@@ -20378,30 +20422,30 @@

 

- <td>
+ <td width="535">
 Add the missing overloads to 28.4 and the
 corresponding later sections in 28 for each swap function.
 We want to accept AMs paper which proposes a single
 overload with two r-value references

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 315

 <td>
 28.4

- <td>
+ <td width="107">
 p6

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 6 Effects:
 string_type str(first, last); return
 use_facet<collate<charT> >(
@@ -20410,60 +20454,60 @@

 

- <td>
+ <td width="535">
 Reword to effect clause to use legal
 iterator dereferences

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 316

 <td>
 28.4 ff

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 The constructors
 for regex classes do not have an r-value overload.

 

- <td>
+ <td width="535">
 Add the missing r-value constructors to
 regex classes.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 317

 <td>
 28.8

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 basic_string has both a constructor and an
 assignment operator that accepts an initializer list,
 basic_regex should have the same.

- <td>
+ <td width="535">
 In the
 basic_regex synopsis, after: basic_regex&
 operator=(const charT* ptr); add: basic_regex&
@@ -20474,23 +20518,23 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 74

 <td>
 28.8

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 
 “basic_regx & operator=
@@ -20499,55 +20543,55 @@
 
 

- <td>
+ <td width="535">
 Add
 basic_regx & operator= (initializer_list<T>);

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 318

 <td>
 28.8.2

- <td>
+ <td width="107">
 para 22

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 Constructor
 definition should appear with the other constructors not
 after assignment ops.

 

- <td>
+ <td width="535">
 Move para 22 to just after para 17.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 319

 <td>
 28.12.2

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 It was always expected that
 regex_token_iterator would be constructible from an array
 literal: indeed ideally this is the prefered method of
@@ -20560,7 +20604,7 @@
 initializer_lists we should use them to remove this
 particular wart.

- <td>
+ <td width="535">
 To the synopsis
 for regex_token_iterator, after template <std::size_t
 N> regex_token_iterator(BidirectionalIterator a,
@@ -20583,84 +20627,84 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 87

 <td>
 29

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 ge

- <td>
+ <td width="510">
 The
 atomics chapter is not concept enabled. The adopted paper,
 N2427, did have those concepts.

 

- <td>
+ <td width="535">
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 311

 <td>
 29

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 Atomic types
 cannot be used generically in a constrained template

 

- <td>
+ <td width="535">
 Provide constraints for the atomics
 library, clause 29

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 312

 <td>
 29

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 The contents of the <stdatomic.h>
 header are not listed anywhere, and <cstdatomic> is
 listed as a C99 header in chapter 17. If we intend to use
 these for compatibility with a future C standard, we should
 not use them now.

- <td>
+ <td width="535">
 Remove <cstdatomic> from the C99
 headers in table 14. Add a new header <atomic> to the
 headers in table 13. Update chapter 29 to remove reference
@@ -20669,28 +20713,28 @@
 adds atomic operations to C we can add corresponding
 headers to table 14 with a TR.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 75

 <td>
 29

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 A
 definition of enum or struct is the style of C using
 typedef.

- <td>
+ <td width="535">
 
 Change to a style of C++.

@@ -20918,29 +20962,29 @@

 }

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 313

 <td>
 29.1

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 seq_cst fences don't necessarily guarantee
 ordering
 http://home.twcny.rr.com/hinnant/cpp_extensions/issues_preview/lwg-active.html#926

- <td>
+ <td width="535">
 Add a new
 paragraph after 29.1 [atomics.order]p5 that says For atomic
 operations A and B on an atomic object M, where A and B
@@ -20951,27 +20995,27 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 88

 <td>
 29.2

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 The "lockfree" facilities do
 not tell the programmer enough.

- <td>
+ <td width="535">
 
 Expand the "lockfree" facilities. See the attached paper
 "Issues with the C++ Standard" under Chapter 29,
@@ -20979,23 +21023,23 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 89

 <td>
 29.3.1

- <td>
+ <td width="107">
 Table 122

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 The
 types in the table "Atomics for standard typedef types"
 should be typedefs, not classes. These semantics are
@@ -21003,31 +21047,31 @@

 

- <td>
+ <td width="535">
 Change the classes to
 typedefs.

- <td>
+ <td width="89">
 Google

 <tr valign="top">
- <td>
+ <td width="29">
 US 90

 <td>
 29.4

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 Are atomic functions allowed
 to have non-volatile overloads?

- <td>
+ <td width="535">
 
 Allow non-volatile overloads. See the attached paper
 "Issues with the C++ Standard, under Chapter 29, "Are
@@ -21035,28 +21079,28 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 91

 <td>
 29.4

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 Whether or not a failed
 compare_exchange is a RMW operation (as used in 1.10
 [intro.multithread]) is unclear.

- <td>
+ <td width="535">
 
 Make failing compare_exchange operations not be RMW. See
@@ -21065,27 +21109,27 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 92

 <td>
 29.4

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 The effect of
 memory_order_consume with atomic RMW operations is unclear.

- <td>
+ <td width="535">
 
 Follow the lead of fences [atomics.fences], and promote
 memory_order_consume to memory_order_acquire with RMW
@@ -21093,23 +21137,23 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 76

 <td>
 30

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 A
 description for "Throws: Nothing." are not unified.

@@ -21117,7 +21161,7 @@
 the part without throw, "Throws: Nothing." should be
 described.

- <td>
+ <td width="535">
 Add
 "Throws: Nothing." to the following.

@@ -21146,36 +21190,36 @@
 
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 93

 <td>
 30

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 ge

- <td>
+ <td width="510">
 The
 thread chapter is not concept enabled.

 

- <td>
+ <td width="535">
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 320
@@ -21185,38 +21229,38 @@
 <td>
 30

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 Threads library cannot be used in
 constrained templates

- <td>
+ <td width="535">
 Provide constraints for the threads
 library, clause 30

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 321

 <td>
 30

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 Throughout this
 clause, the term Requires: is used to introduce compile
 time requirements, which we expect to be replaced with
@@ -21230,32 +21274,32 @@

 

- <td>
+ <td width="535">
 Decument Preconditions: paragraphs in
 17.5.2.4, and use consistently through rest of the library.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 94

 <td>
 30.1.2

- <td>
+ <td width="107">
 1

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 The first sentence of para 1 suggests that no other
 library function is permitted to call operating system or
 low level APIs.

- <td>
+ <td width="535">
 Rewrite para 1
 as: “ Some functions described
@@ -21269,27 +21313,27 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 95

 <td>
 30.1.3

- <td>
+ <td width="107">
 1

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 “native_handle_type” is a typedef, not a
 class member.

- <td>
+ <td width="535">
 Several classes
 described in this Clause have a member native_handle (of
@@ -21306,26 +21350,26 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 96

 <td>
 30.1.4

- <td>
+ <td width="107">
 2

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 There is no definition here for monotonic clock.

- <td>
+ <td width="535">
 Implementations
 should use a monotonic clock to measure time for
@@ -21335,52 +21379,52 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 322

 <td>
 30.1.4

- <td>
+ <td width="107">
 2

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 Not all systms
 can provide a monotonic clock. How are they expected to
 treat a _for function?

 

- <td>
+ <td width="535">
 Add at least a note explaining the intent
 for systems that do not support a monotonic clock.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 323

 <td>
 30.2.1

- <td>
+ <td width="107">
 1

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 The presence of
 a non-explicit variadic template constructor alongside an
 explicit single-argument constructor can lead to behaviour
@@ -21393,37 +21437,37 @@

 

- <td>
+ <td width="535">
 Mark constructor template <class F,
 class ...Args> thread(F&& f, Args&&...
 args); as explicit and remove the single-argument
 constructor.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 324

 <td>
 30.2.1.1

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 thread::id
 objects should be as useable in hashing containers as they
 are in ordered associative containers.

 

- <td>
+ <td width="535">
 Add thread::id
 support for std::hash

@@ -21433,23 +21477,23 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 77

 <td>
 30.2.1.2

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 
 "CopyConstructible" and "MoveConstructible" in
@@ -21460,85 +21504,86 @@
 
 

- <td>
+ <td width="535">
 Add
 a concept for constructor of thread.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 78

 <td>
 30.2.1.2

- <td>
+ <td width="107">
 
 4th para, 1st line

 

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 In
 "F and each Ti in Args", 'Ti' is not clear.

- <td>
+ <td width="535">
 
 Replace "Ti" with "args"

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 97

 <td>
 30.2.1.3

- <td>
+ <td width="107">
 1

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 detach-on-destruction may result in
 “escaped” threads accessing objects with
 bounded lifetime after the end of their lifetime.

- <td>
+ <td width="535">
 See document WG21 N2802=08-0312 written by Hans Boehm.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 US 98

 <td>
- 30.2.1.3, 30.2.1.4
+ 30.2.1.3, 
+ 30.2.1.4

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 

- <td>
+ <td width="510">
 The current defined behavior
 for the std::thread destructor is to detach the thread.
 Unfortunately, this behavior exposes programmers to tricky,
 hard-to-diagnose, undefined behavior.

- <td>
+ <td width="535">
 
 Change destruction behavior to undefined behavior, with a
 note strongly encouraging termination. See the attached
@@ -21547,30 +21592,30 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 325

 <td>
 30.3.3

- <td>
+ <td width="107">
 2

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 We believe constexpr literal values should
 be a more natural expression of empty tag types than extern
 objects as it should improve the compilers ability to
 optimize the empty object away completely.

- <td>
+ <td width="535">
 Replace the
 extern declarations: extern const defer_lock_t defer_lock;
 extern const try_to_lock_t try_to_lock; extern const
@@ -21580,24 +21625,24 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 326

 <td>
 30.3.3.2.1

- <td>
+ <td width="107">
 7

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 The precondition
 that the mutex is not owned by this thread offers
 introduces the risk of un-necessary undefined behaviour
@@ -21611,27 +21656,27 @@

 

- <td>
+ <td width="535">
 Strike 30.3.3.2.1p7

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 327

 <td>
 30.3.3.2.2

- <td>
+ <td width="107">
 4, 9, 14, 19

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 Not clear what
 the specification for error condition
 resource_deadlock_would_occur means. It is perfectly
@@ -21650,65 +21695,65 @@

 

- <td>
+ <td width="535">
 Add a precondition !owns. Change the 'i.e.'
 in the error condition to be 'e.g.' to allow for this
 condition to propogate deadlock detection by the host OS.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 328

 <td>
 30.3.3.2.2

- <td>
+ <td width="107">
 20

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 There is a missing precondition that owns
 is true, or an if(owns) test is missing from the effect
 clause

- <td>
+ <td width="535">
 Add a
 precondition that owns == true. Add an error condition to
 detect a violation, rather than yield undefined behaviour.

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 329

 <td>
 30.5

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 future, promise and packaged_task provide a
 framework for creating future values, but a simple function
 to tie all three components together is missing. Note that
 we only need a *simple* facility for C++0x. Advanced thread
 pools are to be left for TR2.

- <td>
+ <td width="535">
 Provide a simple
 function along the lines of: template< typename F,
 typename ... Args > requires Callable< F, Args...
@@ -21731,58 +21776,58 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 330

 <td>
 30.5.1

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 30.5.1 (and then 30.5.7) refer to a
 specialisation of
 constructible_with_allocator_prefix<> However this
 trait is not in the CD, so references to it should be
 removed.

- <td>
+ <td width="535">
 Remove the
 reference to constructible_with_allocator_prefix in 30.5.1
 Remove paragraph 30.5.7

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 79

 <td>
 30.5.1

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 The
 concept of UsesAllocator and Allocator should be used.

- <td>
+ <td width="535">
 
 Correct as follows.

@@ -21822,24 +21867,24 @@
 
 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 331

 <td>
 30.5.3

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 Not clear what
 it means for a public constructor to be 'exposition only'.
 If the intent is purely to support the library calling this
@@ -21849,29 +21894,29 @@

 

- <td>
+ <td width="535">
 Declare the constructor as private with a
 note about intended friendship, or remove the
 exposition-only comment and document the semantics.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 332

 <td>
 30.5.4

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Ed

- <td>
+ <td width="510">
 It is not clear
 without reference to the original proposal how to use a
 future. In particular, the only way for the user to
@@ -21882,56 +21927,56 @@

 

- <td>
+ <td width="535">
 Provide a small introductory paragraph,
 docuenting intended purpose of the future class template
 and the way futures can only be created via the promise
 API.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 333

 <td>
 30.5.4

- <td>
+ <td width="107">
 5

- <td>
+ <td width="38">
 Ge

- <td>
+ <td width="510">
 We expect the complicated 3-signature
 specifcation for future::get() to be simplified to a single
 signature with a requires clause by the application of
 concepts.

- <td>
+ <td width="535">
 Requires fully baked concepts for clause 30

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 334

 <td>
 30.5.4

- <td>
+ <td width="107">
 5

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 Behaviour of
 get() is undefined if calling get() while not is_ready().
 The intent is that get() is a blocking call, and will wait
@@ -21939,28 +21984,28 @@

 

- <td>
+ <td width="535">
 Effects: If is_ready() would return false,
 block on the asynchronous result associated with *this.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 335

 <td>
 30.5.4

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 
 std::unique_future is MoveConstructible, so you can
 transfer the association with an asynchronous result from
@@ -21974,31 +22019,31 @@

 

- <td>
+ <td width="535">
 Add a "waitable()" function to
 unique_future (and shared_future) akin to
 std::thread::joinable(), which returns true if there is an
 associated result to wait for (whether or not it is ready).
 Then we can say: if(uf.waitable()) uf.wait();

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 336

 <td>
 30.5.4

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 It is possible
 to transfer ownership of the asynchronous result from one
 unique_future instance to another via the move-constructor.
@@ -22012,29 +22057,29 @@

 

- <td>
+ <td width="535">
 Add a default constructor with the
 semantics that it creates a unique_future with no
 associated asynchronous result. Add a move-assignment
 operator which transfers ownership.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 80

 <td>
 30.5.4 , 30.5.5

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 
 Typo, duplicated ">"

@@ -22045,28 +22090,28 @@
 
 

- <td>
+ <td width="535">
 
 Remove one

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 337

 <td>
 30.5.5

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 shared_future
 should support an efficient move constructor that can avoid
 unnecessary manipulation of a reference count, much like
@@ -22074,27 +22119,27 @@

 

- <td>
+ <td width="535">
 Add a move constructor

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 338

 <td>
 30.5.5

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 shared_future is currently
 CopyConstructible, but not CopyAssignable. This is
 inconsistent with shared_ptr, and will surprise users.
@@ -22107,7 +22152,7 @@
 retained by declaring such an instance as "const
 shared_future".

- <td>
+ <td width="535">
 Remove "=delete"
 from the copy-assignment operator of shared_future. Add a
 move-constructor shared_future(shared_future&&
@@ -22122,29 +22167,29 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 339

 <td>
 30.5.6

- <td>
+ <td width="107">
 6, 7

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 Move assignment is goiing in the wrong
 direction, assigning from *this to the passed rvalue, and
 then returning a reference to an unusable *this

- <td>
+ <td width="535">
 Strike 6. 7
 Postcondition: associated state of *this is the same as the
 associated state of rhs before the call. rhs has no
@@ -22152,24 +22197,24 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 340

 <td>
 30.5.6

- <td>
+ <td width="107">
 11, 12, 13

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 There is an
 implied postcondition that the state of the promise is
 transferred into the future leaving the promise with no
@@ -22177,89 +22222,89 @@

 

- <td>
+ <td width="535">
 Postcondition: *this has no associated
 state.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 341

 <td>
 30.5.6

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 promise::swap accepts its parameter by
 lvalue reference. This is inconsistent with other types
 that provide a swap member function, where those swap
 functions accept an rvalue reference

- <td>
+ <td width="535">
 Change promise::swap to take an rvalue
 reference.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 342

 <td>
 30.5.6

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 std::promise is
 missing a non-member overload of swap. This is inconsistent
 with other types that provide a swap member function

 

- <td>
+ <td width="535">
 Add a non-member overload void
 swap(promise&& x,promise&& y){ x.swap(y); }

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 343

 <td>
 30.5.6

- <td>
+ <td width="107">
 3

- <td>
+ <td width="38">
 Te

- <td>
+ <td width="510">
 The move constructor of a std::promise
 object does not need to allocate any memory, so the
 move-construct-with-allocator overload of the constructor
 is superfluous.

- <td>
+ <td width="535">
 Remove the
 constructor with the signature template <class
 Allocator> promise(allocator_arg_t, const Allocator&
@@ -22267,28 +22312,28 @@

 

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 JP 81

 <td>
 30.5.8

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 
 There are not requirements for F and a concept of Allocator
 dose not use.

- <td>
+ <td width="535">
 
 Correct as follows.

@@ -22398,23 +22443,23 @@
 packaged_task(allocator_arg_t, const Alloc& a,
 F&& f);

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 DE-23

 <td>
 Annex B

- <td>
+ <td width="107">
 p2

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 DE-23 Recursive
 use of constexpr functions appears to be permitted. Since
@@ -22422,52 +22467,52 @@
 compile-time, Annex B "implementation quantities" should
 specify a maximum depth of recursion.

- <td>
+ <td width="535">
 In Annex B, specify a recursion depth of 256 or a larger
 value.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 DE-24

 <td>
 Annex B

- <td>
+ <td width="107">
 p2

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 DE-24 The
 number of placeholders for "bind" is implementation-defined
 in 20.7.12.1.4, but no minimum is suggested in Annex B. 

- <td>
+ <td width="535">
 Add a miminum of 10 placeholders to Annex B.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 DE-25

 <td>
 Annex B

- <td>
+ <td width="107">
 p2

- <td>
+ <td width="38">
 te

- <td>
+ <td width="510">
 DE-25
 Specifying a minimum of 17 recursively nested template
@@ -22478,27 +22523,28 @@
 . The conclusion is that the metric "number of recursively
 nested template instantiations" is inapposite.

- <td>
+ <td width="535">
 Remove the bullet "Recursively nested template
 instantiations [17]".

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 FR 38

 <td>
- C.2 [diffs.library]
+ C.2 
+ [diffs.library]

- <td>
+ <td width="107">
 1

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 What is ISO/IEC 1990:9899/DAM
 1? My guess is that's a typo for ISO/IEC

@@ -22508,59 +22554,59 @@
 make reference to things
 which were introduced by Amd.1).

- <td>
+ <td width="535">
 One need probably a reference
 to the document which introduce char16_t and

 char32_t in C (ISO/IEC TR 19769:2004?).

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 UK 
 344

 <td>
 Appendix D

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 Ge

- <td>
+ <td width="510">
 It is desirable to allow some mechanism to
 support phasing out of deprecated features in the future.
 Allowing compilers to implement a mode where deprecated
 features are not available is a good first step.

- <td>
+ <td width="535">
 Add to the definition of deprecated
 features permission for compilers to maintain a
 conditionally supported mode where deprecated features can
 be disabled, so long as they also default to a mode where
 all deprecated features are supported.

- <td>
+ <td width="89">
 

 <tr valign="top">
- <td>
+ <td width="29">
 FR 39

 <td>
 Index

- <td>
+ <td width="107">
 

- <td>
+ <td width="38">
 ed

- <td>
+ <td width="510">
 Some definitions seem not
 indexed (such as /trivially copyable/ or

@@ -22570,10 +22616,10 @@
 increase the usefulness; having a separate index of all
 definitions is something which could also be considered).

- <td>
+ <td width="535">
 

- <td>
+ <td width="89">
 

 </table><hr>
\ No newline at end of file

Next message: bdawes_at_[hidden]: "[Boost-commit] svn:boost r51565 - sandbox/committee/LWG"
Previous message: bdawes_at_[hidden]: "[Boost-commit] svn:boost r51563 - sandbox/committee/LWG"

Date view	Thread view	Subject view	Author view

Boost-Commit list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk