Created on 2012-10-02.00:00:00, last changed 2019-03-24.18:32:03.
This wording is relative to N4810.
Add a new paragraph at the beginning of [re.results.const] as indicated:
Modify [re.results.const] as indicated:
match_results(const match_results& m);
-3- Effects: Constructs
an object of class match_results, asa copy of m.match_results(match_results&& m) noexcept;
-4- Effects: Move constructs
an object of class match_resultsfrom m satisfying the same postconditions as Table 128. Additionally, the stored Allocator value is move constructed from m.get_allocator(). -5- Throws: Nothing.match_results& operator=(const match_results& m);
-6- Effects: Assigns m to *this.
The postconditions of this function are indicated in Table 128.match_results& operator=(match_results&& m);
-7- Effects: Move
-assigns m to *this. The postconditions of this function are indicated in Table 128.
Modify [re.results.const], Table 128 — "match_results assignment operator effects", as indicated:
Table 128 — match_results assignment operator effects Element Value ready() m.ready() size() m.size() str(n) m.str(n) for all integers n < m.size() prefix() m.prefix() suffix() m.suffix() (*this)[n] m[n] for all integers n < m.size() length(n) m.length(n) for all integers n < m.size() position(n) m.position(n) for all integers n < m.size()
[ 2019-03-26; Daniel comments and provides wording ]
The previous Table 141 (Now Table 128 in N4810) has been modified to cover now the effects of move/copy constructors and move/copy assignment operators. Newly added wording now clarifies that for move operations the corresponding values refer to the values of the move source before the operation has started.Re Ganesh's proposal: Note that no further wording is needed for the move-assignment operator, because in the current working draft the move-assignment operator's Effects: element refers already to Table 128. The suggested clarification of unsigned integers has been implemented by referring to non-negative integers instead. Upon suggestion from Casey, the wording also introduces Ensures: elements that refer to Table 128 and as drive-by fix eliminates a "Throws: Nothing." element from a noexcept function.
[re.results.const]/3: "Move-constructs an object of class match_results satisfying the same postconditions as Table 141."
Table 141 lists various member functions and says that their results should be the results of the corresponding member function calls on m. But m has been moved from, so the actual requirement ought to be based on the value that m had before the move construction, not on m itself.
In addition to that, the requirements for the copy constructor should refer to Table 141.Ganesh: Also, the requirements for move-assignment should refer to Table 141. Further it seems as if in Table 141 all phrases of "for all integers n < m.size()" should be replaced by "for all unsigned integers n < m.size()".
|2019-03-24 18:32:03||admin||set||messages: + msg10378|
|2019-03-24 18:32:03||admin||set||messages: + msg10377|