Drive-by stop calling .base() on test iterators in the test, and improve the transform_view::iterator/sentinel tests.
Details
- Reviewers
ldionne Mordante - Group Reviewers
Restricted Project - Commits
- rG4b3e0d2a7eb7: [libc++] Fix LWG3533 "Make `base() const&` consistent..."
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
LGTM, but I think we suffer from the same problem in other iterators, for example transform_view::iterator but probably others too. Any appetite for fixing all of them in this PR?
Turns out that transform_view::iterator is the only other one, that we've already implemented, that doesn't require major other changes for C++20.
move_iterator and reverse_iterator are also affected but require major changes for C++20 that we haven't implemented yet.
filter_view::iterator is affected but we haven't implemented it yet.
lazy_split_view::iterator is affected but we haven't implemented it yet.
elements_view::iterator is affected but we haven't implemented it yet.
Turns out this is LWG3533; so now we can mark that issue Complete.
CI is still green.
Please add this to the commit message and mention [range.elements.iterator] has been omitted since we haven't implemented that yet.
(I expect the person implementing that to use the current wording in the Standard.)
LTGM!