public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/106201] filesystem::directory_iterator is a borrowable range? Date: Tue, 22 Nov 2022 12:33:04 +0000 [thread overview] Message-ID: <bug-106201-4-zivKJA1VTG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106201-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106201 --- Comment #10 from Jonathan Wakely <redi at gcc dot gnu.org> --- I'm planning to use this workaround for gcc-11 and gcc-12: --- a/libstdc++-v3/include/bits/fs_path.h +++ b/libstdc++-v3/include/bits/fs_path.h @@ -737,7 +737,14 @@ namespace __detail /// @{ /// @relates std::filesystem::path +#if __cpp_concepts >= 201907L + // Workaround for PR libstdc++/106201 + inline void + swap(same_as<path> auto& __lhs, same_as<path> auto& __rhs) noexcept + { __lhs.swap(__rhs); } +#else inline void swap(path& __lhs, path& __rhs) noexcept { __lhs.swap(__rhs); } +#endif size_t hash_value(const path& __p) noexcept; This will prevent that swap overload from being a candidate for swapping counted_iterator<filesystem::directory_iterator>, so we won't check for conversion to path& and hit the constraint recursion.
next prev parent reply other threads:[~2022-11-22 12:33 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-05 13:28 [Bug libstdc++/106201] New: " prlw1 at cam dot ac.uk 2022-07-05 14:11 ` [Bug libstdc++/106201] " redi at gcc dot gnu.org 2022-07-05 15:23 ` redi at gcc dot gnu.org 2022-07-05 15:31 ` redi at gcc dot gnu.org 2022-07-05 15:59 ` redi at gcc dot gnu.org 2022-07-19 18:05 ` cvs-commit at gcc dot gnu.org 2022-07-21 14:51 ` prlw1 at cam dot ac.uk 2022-07-21 14:52 ` redi at gcc dot gnu.org 2022-07-21 14:54 ` redi at gcc dot gnu.org 2022-07-21 14:59 ` prlw1 at cam dot ac.uk 2022-11-22 12:33 ` redi at gcc dot gnu.org [this message] 2022-11-22 17:54 ` cvs-commit at gcc dot gnu.org 2022-11-22 21:49 ` cvs-commit at gcc dot gnu.org 2022-11-25 0:21 ` cvs-commit at gcc dot gnu.org 2023-10-04 9:18 ` redi at gcc dot gnu.org 2024-03-08 21:47 ` ppalka at gcc dot gnu.org
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=bug-106201-4-zivKJA1VTG@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).