Implement std::ranges view support in matchers
#4893
+171
−17
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.
std::rangesandstd::views::as_constdetection.StlContainerViewwith astd::ranges::viewspecialization.internal::ValueTypeto deduce element/value type for both STL containers and ranges, while keeping backward-compatibility for the existing behavior.internal::ValueTypeinstead of assuming nestedvalue_type.std::rangesviews (e.g.ElementsAre,ElementsAreArray,Contains,Pointwise,UnorderedPointwise,Pointee).Tested: On x86_64-pc-linux-gnu, with gcc 15.2.1 and clang 21.1.6, with libstdc++ for both, with build types Debug and Release, with C++ standards 17, 20 and 23.
Ad-hoc test script is given below.