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++/103923] is_invocable<const T &, ...> inexplicably fails
Date: Thu, 06 Jan 2022 09:37:36 +0000 [thread overview]
Message-ID: <bug-103923-4-UAZAHH1DfG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103923-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103923
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2022-01-06
Status|UNCONFIRMED |NEW
Ever confirmed|0 |1
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
The problem is actually that the auto return type can't be deduced while the
enclosing class is incomplete, not that H is incomplete.
N.B. You can fix your code by simply changing the return type to not use auto:
struct H {
int operator()(const K &) const { return 0; }
};
In any case, I think changing libstdc++ to make the code ill-formed would be an
improvement than silently compiling it but getting the traits wrong.
next prev parent reply other threads:[~2022-01-06 9:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-05 23:16 [Bug c++/103923] New: " jengelh at inai dot de
2022-01-05 23:19 ` [Bug libstdc++/103923] " pinskia at gcc dot gnu.org
2022-01-06 9:23 ` redi at gcc dot gnu.org
2022-01-06 9:31 ` redi at gcc dot gnu.org
2022-01-06 9:37 ` redi at gcc dot gnu.org [this message]
2022-01-06 9:39 ` redi at gcc dot gnu.org
2022-01-06 9:46 ` redi at gcc dot gnu.org
2022-01-06 14:30 ` redi at gcc dot gnu.org
2022-01-06 14:53 ` redi at gcc dot gnu.org
2022-01-06 16:00 ` redi 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-103923-4-UAZAHH1DfG@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).