Fix noexcept specifier expressions for move operations #93
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 pull request fixes the noexcept specifier expressions for the move constructor and the move assignment operator.
For the move constructor, version P0323R10 of the proposal has the following remark:
The expression inside noexcept is equivalent to:
The fix is separated into two commits, the first adds the or-T-is-void part, and the second adds the requirement on E. Test code is included to show the effects of the changes.
For the move assignment operator, the proposal has the following remark:
The expression inside noexcept is equivalent to: is_nothrow_move_assignable_v is true and is_nothrow_move_constructible_v is true.
The fix assumes that the above remark is in error, and that it should be:
The expression inside noexcept is equivalent to:
Again the fix is separated into two commits and includes test code.