-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Implement ranges::elements_view #1406
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
Conversation
Co-authored-by: S. B. Tam <cpplearner@outlook.com>
|
Note that |
Awesome, thanks for the heads up 😺 |
Co-authored-by: Casey Carter <cartec69@gmail.com> Co-authored-by: S. B. Tam <cpplearner@outlook.com>
CaseyCarter
left a comment
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.
Changes look good - I think we're only missing some conditional noexcept test coverage now (#1406 (comment)).
product code: * Define `iterator_concept` so the view can adapt ranges whose iterators have no `iterator_category` (This is how we've dealt with LWG-3289 elsewhere.) * Don't try to modify members of constant iterators * `_Sentinel`'s friends are not friends of `_Iterator` test: * Silence shadowing warnings by using the global `expected_keys` and `expected_values` instead of passing them to `test_one` via parameters with the same names. * Replace references to `EV` with `R` since they name the same type * Don't `forward` the same rvalue input range repeatedly
CaseyCarter
left a comment
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.
Changes look good - I think we're only missing some conditional
noexcepttest coverage now (#1406 (comment)).
Nice try, but you were wrong. Fixed up a few small issues and I think this is now good to go.
StephanTLavavej
left a comment
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.
(This is a very incomplete review; I'll resume reviewing later this week)
StephanTLavavej
left a comment
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.
This looks great, thanks! All I found were extremely minor nitpicks so I'll validate and push changes.
StephanTLavavej
left a comment
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.
@CaseyCarter I pushed small changes after you approved.
... and resolve `common_view` vs. `elements_view` conflict by relocating `common_view` before `reverse_view` where it belongs.
@StephanTLavavej I pushed what look like bug changes after you approved: |
Err, "big changes". This is too funny to edit in place, I'm leaving the typo for posterity ;) |
|
FYI @CaseyCarter, I've pushed a fix after you approved, working around an internal compiler assertion in the test that I've reduced and reported. |
|
|
Thanks for implementing these crucial elements of ranges; customers will be able to view them in VS 2019 16.9 Preview 2. 😹 |
This is not fully functional as I has hit a roadblock, trying to understand why
ranges::view<EV>breaks due toranges::endnot being available.@CaseyCarter: any ideas what is going on here?