From: Hans-Peter Nilsson <hp@axis.com>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: <libstdc++@gcc.gnu.org>, <gcc-patches@gcc.gnu.org>
Subject: Re: [committed v2] libstdc++: Define std::ranges::to for C++23 (P1206R7) [PR111055]
Date: Tue, 28 Nov 2023 01:02:39 +0100 [thread overview]
Message-ID: <20231128000239.12DC220448@pchp3.se.axis.com> (raw)
In-Reply-To: <20231123175247.2451163-1-jwakely@redhat.com> (message from Jonathan Wakely on Thu, 23 Nov 2023 17:51:38 +0000)
> From: Jonathan Wakely <jwakely@redhat.com>
> Date: Thu, 23 Nov 2023 17:51:38 +0000
> libstdc++-v3/ChangeLog:
>
> PR libstdc++/111055
> * include/bits/ranges_base.h (from_range_t): Define new tag
> type.
> (from_range): Define new tag object.
> * include/bits/version.def (ranges_to_container): Define.
> * include/bits/version.h: Regenerate.
> * include/std/ranges (ranges::to): Define.
> * testsuite/std/ranges/conv/1.cc: New test.
> * testsuite/std/ranges/conv/2_neg.cc: New test.
> * testsuite/std/ranges/conv/version.cc: New test.
JFTR, for the list: this (r14-5794-g7a6a29c455e775) caused
another one of those wonderful "xtreme test" regressions.
Logged as PR112737: "[14 Regression]
g++.dg/modules/xtreme-header-2_b.C -std=c++2b (test for
excess errors)", and pinskia quickly linked it to the
meta-bug for modules issues, PR103524 (thanks!)
IIRC, sometimes those tests show bugs elsewhere, suggesting
lack of coverage in other tests (and not just streaming
aspects), but this one actually mentions modules in key
error messages.
brgds, H-P
next prev parent reply other threads:[~2023-11-28 0:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-17 15:49 [PATCH] " Jonathan Wakely
2023-11-23 17:51 ` [committed v2] " Jonathan Wakely
2023-11-28 0:02 ` Hans-Peter Nilsson [this message]
2023-11-29 16:28 ` Patrick Palka
2023-11-30 15:49 ` Jonathan Wakely
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231128000239.12DC220448@pchp3.se.axis.com \
--to=hp@axis.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely@redhat.com \
--cc=libstdc++@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).