public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
From: Patrick Palka <ppalka@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc r13-2629] libstdc++: Add already-accepted <ranges> testcase [PR106320]
Date: Mon, 12 Sep 2022 19:05:57 +0000 (GMT)	[thread overview]
Message-ID: <20220912190557.D44C43858403@sourceware.org> (raw)

https://gcc.gnu.org/g:db19cfdac8ede93172aecc58612171c239c993ad

commit r13-2629-gdb19cfdac8ede93172aecc58612171c239c993ad
Author: Patrick Palka <ppalka@redhat.com>
Date:   Mon Sep 12 15:05:04 2022 -0400

    libstdc++: Add already-accepted <ranges> testcase [PR106320]
    
    Although PR106320 affected only the 10 and 11 branches, and the testcase
    from there is already correctly accepted on trunk and the 12 branch, we
    still should add the testcase to trunk/12 too for inter-branch consistency.
    
            PR libstdc++/106320
    
    libstdc++-v3/ChangeLog:
    
            * testsuite/std/ranges/adaptors/join.cc (test13): New test.

Diff:
---
 libstdc++-v3/testsuite/std/ranges/adaptors/join.cc | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/libstdc++-v3/testsuite/std/ranges/adaptors/join.cc b/libstdc++-v3/testsuite/std/ranges/adaptors/join.cc
index 8986f718229..530ab6663b5 100644
--- a/libstdc++-v3/testsuite/std/ranges/adaptors/join.cc
+++ b/libstdc++-v3/testsuite/std/ranges/adaptors/join.cc
@@ -205,6 +205,18 @@ test12()
   }();
 }
 
+void
+test13()
+{
+  // PR libstdc++/106320
+  auto l = std::views::transform([](auto x) {
+    return x | std::views::transform([i=0](auto y) {
+      return y;
+    });
+  });
+  std::vector<std::vector<int>> v{{5, 6, 7}};
+  v | l | std::views::join;
+}
 int
 main()
 {
@@ -220,4 +232,5 @@ main()
   test10();
   test11();
   test12();
+  test13();
 }

                 reply	other threads:[~2022-09-12 19:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220912190557.D44C43858403@sourceware.org \
    --to=ppalka@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    --cc=libstdc++-cvs@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).