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++/96286] Unhelpful errors after a failed static_assert
Date: Thu, 15 Jul 2021 11:21:51 +0000 [thread overview]
Message-ID: <bug-96286-4-eQrP00xZXo@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96286-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96286
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #2)
> Why is the compiler even doing overload resolution for std::get<I> if I is
> an invalid constant expression?! It's not going to match any overload!
This part is now PR 101460
next prev parent reply other threads:[~2021-07-15 11:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 15:00 [Bug c++/96286] New: " redi at gcc dot gnu.org
2021-07-15 10:44 ` [Bug c++/96286] " redi at gcc dot gnu.org
2021-07-15 10:56 ` redi at gcc dot gnu.org
2021-07-15 11:21 ` redi at gcc dot gnu.org [this message]
2021-08-30 21:27 ` cvs-commit at gcc dot gnu.org
2021-08-31 21:48 ` jason at gcc dot gnu.org
2021-09-02 12:27 ` jason at gcc dot gnu.org
2021-09-02 12:27 ` jason at gcc dot gnu.org
2021-09-02 12:56 ` 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-96286-4-eQrP00xZXo@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).