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++/99692] Lookup for operator<< skips global scope
Date: Thu, 06 May 2021 12:12:49 +0000 [thread overview]
Message-ID: <bug-99692-4-KBYLvNvo2d@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99692-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99692
--- Comment #11 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #10)
> template<typename _Ostream, typename _Tp>
> struct __is_insertable<_Ostream, _Tp,
> void_t<decltype(declval<_Ostream&>()
> << declval<const _Tp&>())>>
The problem is that this check produces a hard error (rather than substitution
failure) for declval<std::ostream&>() << declval<const N::A&>().
The relevant operator is not found by ADL, because it's not in the associated
namespaces of std::ostream or N::A (which is IMHO a design error in the code,
but nevermind). So the void_t expression should get a substitution error.
I think the problem is that PR 51577 causes GCC to look in the global scope and
so incorrectly find the declaration of:
std::ostream& operator<<(std::ostream& s, const N::A&)
which means that the __is_insertable check ... goes wrong somehow? I think it
makes the void_t expression ambiguous because of the global operator<< overload
which is not meant to be found.
The reduced example above can be reduced further:
namespace std
{
struct ostream { };
template<typename T> T&& declval();
template<typename...> using void_t = void;
struct false_type { static constexpr bool value = false; };
struct true_type { static constexpr bool value = true; };
template<typename _Ostream, typename _Tp, typename = void>
struct __is_insertable : false_type {};
template<typename _Ostream, typename _Tp>
struct __is_insertable<_Ostream, _Tp,
void_t<decltype(declval<_Ostream&>()
<< declval<const _Tp&>())>>
: true_type {};
}
struct CustomStream : std::ostream {};
namespace N {
class A{};
}
std::ostream& operator<<(std::ostream& s, const N::A&)
{
return s;
}
int main()
{
static_assert( ! std::__is_insertable<std::ostream, N::A>::value, "" );
}
This avoids the hard error in __is_insertable, but GCC fails the static_assert
(where as Clang passes it) which is PR 51577.
next prev parent reply other threads:[~2021-05-06 12:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-21 4:01 [Bug c++/99692] New: " skaniskin at berkeley dot edu
2021-03-21 5:26 ` [Bug libstdc++/99692] " pinskia at gcc dot gnu.org
2021-03-21 5:28 ` pinskia at gcc dot gnu.org
2021-03-21 6:01 ` skaniskin at gmail dot com
2021-03-21 12:21 ` redi at gcc dot gnu.org
2021-03-21 12:23 ` redi at gcc dot gnu.org
2021-03-21 13:56 ` skaniskin at gmail dot com
2021-03-21 23:24 ` redi at gcc dot gnu.org
2021-05-06 4:07 ` [Bug c++/99692] " skaniskin at gmail dot com
2021-05-06 9:05 ` redi at gcc dot gnu.org
2021-05-06 9:38 ` redi at gcc dot gnu.org
2021-05-06 12:12 ` redi at gcc dot gnu.org [this message]
2021-05-06 13:07 ` redi at gcc dot gnu.org
2021-12-16 18: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-99692-4-KBYLvNvo2d@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).