public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/96926] [9/10/11 Regression] Tuple element w/ member reference to incomplete template type rejected
Date: Fri, 12 Feb 2021 05:09:18 +0000 [thread overview]
Message-ID: <bug-96926-4-m6aUbZ0zTh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96926-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96926
--- Comment #5 from Jason Merrill <jason at gcc dot gnu.org> ---
(In reply to Jason Merrill from comment #4)
> I think perhaps it's wrong to do substitution at this point because X has no
> default argument. Giving it a default argument causes clang 10 to also
> reject the testcase.
...but changing that doesn't help real testcases, since the tuple constructors
do have default args for their constructor parms.
next prev parent reply other threads:[~2021-02-12 5:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 16:17 [Bug c++/96926] New: " redi at gcc dot gnu.org
2020-09-03 16:18 ` [Bug c++/96926] " redi at gcc dot gnu.org
2020-09-03 16:19 ` redi at gcc dot gnu.org
2020-09-03 18:26 ` redi at gcc dot gnu.org
2020-09-04 6:36 ` rguenth at gcc dot gnu.org
2020-10-12 12:25 ` rguenth at gcc dot gnu.org
2021-02-12 3:24 ` jason at gcc dot gnu.org
2021-02-12 5:00 ` jason at gcc dot gnu.org
2021-02-12 5:09 ` jason at gcc dot gnu.org [this message]
2021-02-13 6:12 ` jason at gcc dot gnu.org
2021-02-19 2:22 ` cvs-commit at gcc dot gnu.org
2021-02-19 4:01 ` cvs-commit at gcc dot gnu.org
2021-02-25 16:34 ` [Bug c++/96926] [9/10 " jason at gcc dot gnu.org
2021-06-01 8:18 ` rguenth at gcc dot gnu.org
2022-05-13 15:25 ` jason 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-96926-4-m6aUbZ0zTh@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).