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 c++/94894] Premature instantiation of conversion function template during overload resolution
Date: Tue, 05 Jul 2022 16:08:13 +0000 [thread overview]
Message-ID: <bug-94894-4-atKbLVXnUt@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94894-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94894
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
CC| |redi at gcc dot gnu.org
Ever confirmed|0 |1
Last reconfirmed| |2022-07-05
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
>From PR libstdc++/106201:
struct foo
{
template<typename T, typename = decltype(f(*(T*)nullptr))>
foo(const T&) { }
};
struct bar { };
struct baz
{
template<typename T> baz(const T&) { }
};
void f(foo&);
void f(baz);
int main()
{
bar b;
f(b);
}
G++ goes into infinite recursion, Clang, EDG and MSVC accept it.
That was reduced from one using concepts:
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);
}
next prev parent reply other threads:[~2022-07-05 16:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 18:10 [Bug c++/94894] New: " ppalka at gcc dot gnu.org
2022-07-05 16:08 ` redi at gcc dot gnu.org [this message]
2022-07-15 15:14 ` [Bug c++/94894] avoidable " ppalka at gcc dot gnu.org
2022-07-19 18:05 ` cvs-commit 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-94894-4-atKbLVXnUt@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).