From: Tim Song <t.canens.cpp@gmail.com>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: "libstdc++" <libstdc++@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>,
Tim Shen <timshen@google.com>
Subject: Re: [PATCH] PR libstdc++/80939 Remove unmeetable constexpr specifiers
Date: Sun, 11 Jun 2017 00:15:00 -0000 [thread overview]
Message-ID: <CAPQZVxvJWjSRwEMwyFeXjNTq4q=m-KJy5znfAGyMXpVtuQ2uUA@mail.gmail.com> (raw)
In-Reply-To: <20170602130734.GA6233@redhat.com>
On Fri, Jun 2, 2017 at 9:07 AM, Jonathan Wakely <jwakely@redhat.com> wrote:
> we aren't qualifying calls to __ref_cast,
Turns out this is fine. I somehow managed to completely misread the
last sentence of [basic.lookup.argdep]/2. It's talking about the case
where an argument to the call is a set of overloaded functions named
by a template-id, not about the postfix-expression.
At least qualifying those calls doesn't hurt either.
Sorry :(
prev parent reply other threads:[~2017-06-11 0:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 13:07 Jonathan Wakely
2017-06-02 19:19 ` Tim Shen via gcc-patches
2017-06-02 19:40 ` Tim Song
2017-06-05 16:49 ` Jonathan Wakely
2017-06-11 0:15 ` Tim Song [this message]
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='CAPQZVxvJWjSRwEMwyFeXjNTq4q=m-KJy5znfAGyMXpVtuQ2uUA@mail.gmail.com' \
--to=t.canens.cpp@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely@redhat.com \
--cc=libstdc++@gcc.gnu.org \
--cc=timshen@google.com \
/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).