[func.wrap.func.cons] [any.assign] Harmonize operator= wording #6746
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This harmonizes the wording of
operator=
semantics for all four type-erasure types (function, any, move_only_function, copyable_function) by bringing the former two into line with the latter (newer) two.Using "Equivalent to" instead of "As if by" allows us to omit some wording about what exceptions might be thrown. [func.wrap.func.con] also had a typo "As if by
x;
" that should have been "As if byx
."The one borderline-editorial part is
function
's move-constructor ([func.wrap.func.cons]/21). The old wording is"Replaces the target of
*this
with the target off
," which a sufficiently smart vendor could take as giving permission to use the contained object's assignment operator (iff
's contained object is assignable to*this
's contained object) and/or to destroy*this
's contained object before copyingf
's contained object. My impression is that no vendor (ab)uses that permission today, but please correct me if I'm wrong.