public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93595] [c++20] function call, substitution failure of template paramter with a lambda default in template context
Date: Tue, 11 Jul 2023 14:44:30 +0000 [thread overview]
Message-ID: <bug-93595-4-0hDtFrnV54@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-93595-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93595
--- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Ted Lyngmo from comment #6)
> @Andrew Pinski: Shouldn't the status be "CONFIRMED" rather than "NEW"?
There is status called confirmed but rather rhe new status is the confirmed
state.
next prev parent reply other threads:[~2023-07-11 14:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-93595-4@http.gcc.gnu.org/bugzilla/>
2021-12-20 6:12 ` [Bug c++/93595] [c++20] Substitution failure of "auto = []{}" in template parameter list in nested " pinskia at gcc dot gnu.org
2021-12-20 6:12 ` pinskia at gcc dot gnu.org
2021-12-20 6:55 ` [Bug c++/93595] [c++20] function call, substitution failure of template paramter with a lambda default in " pinskia at gcc dot gnu.org
2023-07-11 13:42 ` ppalka at gcc dot gnu.org
2023-07-11 14:42 ` ted at lyncon dot se
2023-07-11 14:44 ` pinskia at gcc dot gnu.org [this message]
2023-07-11 14:46 ` ted at lyncon dot se
2024-03-25 10:55 ` [Bug c++/93595] [c++20] function call, substitution failure of template parameter " andrea.agostini.sax at gmail dot com
2024-03-25 19:05 ` ppalka at gcc dot gnu.org
2024-04-12 19:21 ` ppalka at gcc dot gnu.org
2024-04-12 19:21 ` 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-93595-4-0hDtFrnV54@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).