public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jonathan Wakely <redi@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc r13-4242] libstdc++: Add testcase for fs::path constraint recursion [PR106201]
Date: Tue, 22 Nov 2022 17:54:39 +0000 (GMT)	[thread overview]
Message-ID: <20221122175439.D018D3858C27@sourceware.org> (raw)

https://gcc.gnu.org/g:6b859736bb1e707778627b2e58ef6088e475a54c

commit r13-4242-g6b859736bb1e707778627b2e58ef6088e475a54c
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Tue Nov 22 12:17:27 2022 +0000

    libstdc++: Add testcase for fs::path constraint recursion [PR106201]
    
    libstdc++-v3/ChangeLog:
    
            PR libstdc++/106201
            * testsuite/27_io/filesystem/iterators/106201.cc: New test.

Diff:
---
 libstdc++-v3/testsuite/27_io/filesystem/iterators/106201.cc | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/libstdc++-v3/testsuite/27_io/filesystem/iterators/106201.cc b/libstdc++-v3/testsuite/27_io/filesystem/iterators/106201.cc
new file mode 100644
index 00000000000..4a64e675816
--- /dev/null
+++ b/libstdc++-v3/testsuite/27_io/filesystem/iterators/106201.cc
@@ -0,0 +1,12 @@
+// { dg-options "-std=gnu++20" }
+// { dg-do compile { target c++20 } }
+// { dg-require-filesystem-ts "" }
+
+// PR libstdc++/106201 constraint recursion in path(Source const&) constructor.
+
+#include <filesystem>
+#include <ranges>
+using I = std::counted_iterator<std::filesystem::directory_iterator>;
+static_assert( std::swappable<I> );
+using R = std::counted_iterator<std::filesystem::recursive_directory_iterator>;
+static_assert( std::swappable<R> );

                 reply	other threads:[~2022-11-22 17:54 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=20221122175439.D018D3858C27@sourceware.org \
    --to=redi@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).