diff options
author | Jakub Jelinek <jakub@redhat.com> | 2025-08-05 08:27:05 +0200 |
---|---|---|
committer | Jakub Jelinek <jakub@gcc.gnu.org> | 2025-08-05 08:27:05 +0200 |
commit | 1e8ee6fa93caef91f518c4b6be0fb9b7d140abfd (patch) | |
tree | db68a55d4478727ddcf734aa0f638e2024e51160 /gcc/testsuite/c-c++-common/goacc/routine-3.c | |
parent | ab7c16990fca6b456156895d8d0d5e1a37476d38 (diff) | |
download | gcc-master.zip gcc-master.tar.gz gcc-master.tar.bz2 |
On Mon, Aug 04, 2025 at 11:33:17AM -0400, Patrick Palka wrote:
> > @@ -1693,6 +1697,8 @@ export namespace std
> > {
> > using std::ranges::advance;
> > using std::ranges::distance;
> > + using std::ranges::iter_move;
> > + using std::ranges::iter_swap;
>
> Actually a few lines above we already do:
>
> // _Cpo is an implementation detail we can't avoid exposing; if we do the
> // using in ranges directly, it conflicts with any friend functions of the
> // same name, which is why the customization points are in an inline
> // namespace in the first place.
> namespace ranges::inline _Cpo
> {
> using _Cpo::iter_move;
> using _Cpo::iter_swap;
> }
>
> So I think we don't want to export iter_move and iter_swap directly... Sorry
> for not catching this sooner :/
Here is a patch which does that.
2025-08-05 Jakub Jelinek <jakub@redhat.com>
PR libstdc++/121373
* src/c++23/std.cc.in (std::ranges::iter_move, std::ranges::iter_swap):
Remove exports.
Diffstat (limited to 'gcc/testsuite/c-c++-common/goacc/routine-3.c')
0 files changed, 0 insertions, 0 deletions