diff options
author | Jonathan Wakely <jwakely@redhat.com> | 2021-12-12 21:16:25 +0000 |
---|---|---|
committer | Jonathan Wakely <jwakely@redhat.com> | 2021-12-13 11:15:41 +0000 |
commit | 55823c5a0ba50022d7fcc95e74ec293143810ef6 (patch) | |
tree | 42fe968367bd37354d599b1ea8396344dba783f6 /gcc | |
parent | ef5d671cd80a4afa4f74c3dfe2904c63f51fcfde (diff) | |
download | gcc-55823c5a0ba50022d7fcc95e74ec293143810ef6.zip gcc-55823c5a0ba50022d7fcc95e74ec293143810ef6.tar.gz gcc-55823c5a0ba50022d7fcc95e74ec293143810ef6.tar.bz2 |
libstdc++: Make ranges::size and ranges::empty check for unbounded arrays
Passing IncompleteType(&)[] to ranges::begin produces an error outside
the immediate context, which is fine for ranges::begin, but it means
that we fail to enforce the SFINAE-able constraints for ranges::size and
ranges::size. They should not be callable for any array of unknown
bound, whether the type is complete or not. Because we don't enforce
that in their constraints, we get a hard error when they try to use
ranges::begin.
This simply adds explicit checks for arrays of unknown bound to the
constraints for ranges::size and ranges::empty. We only need to check it
for the __sentinel_size and __eq_iter_empty concepts, because those are
the ones that are relevant to arrays, and which try to use
ranges::begin.
libstdc++-v3/ChangeLog:
* include/bits/ranges_base.h (ranges::size, ranges::empty): Add
explicit check for unbounded arrays before using ranges::begin.
* testsuite/std/ranges/access/empty.cc: Check handling of unbounded
arrays.
* testsuite/std/ranges/access/size.cc: Likewise.
Diffstat (limited to 'gcc')
0 files changed, 0 insertions, 0 deletions