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, 05 Jul 2022 15:23:54 +0000 [thread overview]
Message-ID: <bug-106201-4-YnTHkXI5rD@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 #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #1)
> The third one fails but not because of anything to do with borrowable
> ranges. The problem is that the filesystem::swap(path&, path&) overload is
> found by ADL and considered by overload resolution when checking whether
> counted_iterator<filesystem::directory_iterator> is swappable. Overload
> resolution checks whether the iterator can be converted to a path, which
> causes constraint recursion.
The full explanation is that views::take creates a view whose iterator is
counted_iterator<filesystem::directory_iterator> and the constraints for
ranges::for_each check that that iterator is copyable, movable, and swappable.
That fails with libstdc++:
#include <filesystem>
#include <ranges>
using I = std::counted_iterator<std::filesystem::directory_iterator>;
static_assert( std::swappable<I> );
The swappable concept finds filesystem::swap(path&, path&) via ADL. Overload
resolution checks if counted_iterator<filesystem::directory_iterator> can be
converted to path, which considers the path constructors, which checks if
counted_iterator is an iterator, which uses std::iterator_traits, which depends
on the iterator being copyable, which depends on it being swappable, and we're
recursing.
However, I *think* there's a compiler bug here. We should not be considering
constructors of path to see if we can get a path& lvalue. That would never
work, constructing a path would give us an rvalue. Clang compiles the example
when using libstdc++ headers.
Clang and EDG both compile this, but G++ doesn't:
namespace effing
{
template<typename T>
concept effable = requires (T& t) { f(t); };
template <class T>
requires effable<T> || true
void eff(T&&) { }
}
struct path {
template<effing::effable T> path(const T&) { }
};
void f(path&);
struct iterator { };
int main()
{
iterator i;
effing::eff(i);
}
conv.C: In substitution of 'template<class T> requires effable<T>
path::path(const T&) [with T = iterator]':
conv.C:4:42: recursively required by substitution of 'template<class T>
requires effable<T> path::path(const T&) [with T = iterator]'
conv.C:4:42: required by substitution of 'template<class T> requires
(effable<T>) || true void effing::eff(T&&) [with T = iterator&]'
conv.C:22:14: required from here
conv.C:4:13: required for the satisfaction of 'effable<T>' [with T =
iterator]
conv.C:4:23: in requirements with 'T& t' [with T = iterator]
conv.C:4:23: error: satisfaction of atomic constraint 'requires(T& t) {f(t);}
[with T = T]' depends on itself
4 | concept effable = requires (T& t) { f(t); };
| ^~~~~~~~~~~~~~~~~~~~~~~~~
next prev parent reply other threads:[~2022-07-05 15:23 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 [this message]
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
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-YnTHkXI5rD@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: 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).