-
Notifications
You must be signed in to change notification settings - Fork 1.6k
improve iota_view's iterator's binary operator+ (LWG-3580) #2417
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Stephan T. Lavavej (StephanTLavavej)
merged 3 commits into
microsoft:main
from
fsb4000:fix2398
Dec 17, 2021
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Casey Carter (@CaseyCarter) I observe that this one says
is_nothrow_move_constructible_v<_Wi>but the other two saidis_nothrow_move_constructible_v<_Ioterator>. You mentioned that they're equivalent, and there seems to be a rationale (as this one constructs an_Ioteratorprvalue), but I wanted to point this out in case it was unintentional and should be cleaned up later. No change requested here.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The other two functions return an lvalue denoting a variable with automatic storage duration, so they are implicitly moved, and that variable is a function argument, so they cannot benefit from NRVO or RVO. Consequently they move construct an
_Ioterator.This function returns a prvalue, so no
_Ioterators are moved or copied - C++17 delayed temporary materialization kicks in. It does need to account for potential throws from the_Ioteratorconstructor from_Wi, however. That constructor is annotated withnoexcept(is_nothrow_move_constructible_v<_Wi>. I'm not sure why I decided to "inline" thatnoexcept-specifier instead of using the more directis_nothrow_constructible_v<_Ioterator, _Wi>. I really need to work at making my conditionalnoexceptstyle more consistent.