From: Jason Merrill <jason@redhat.com>
To: Marek Polacek <polacek@redhat.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: C++ PATCH to implement deferred parsing of noexcept-specifiers (c++/86476, c++/52869)
Date: Wed, 12 Jun 2019 03:46:00 -0000 [thread overview]
Message-ID: <6949597a-e84c-4b87-ec57-f0186b936101@redhat.com> (raw)
In-Reply-To: <20190604010137.GY5989@redhat.com>
On 6/3/19 9:01 PM, Marek Polacek wrote:
> I sort of ended up going down a rathole, but then I realized we don't need to
> delay parsing of noexcept-specifiers of member friend function declarations,
> because they aren't members of the class.
Where are you getting this from? I'm definitely sympathetic to the idea
that noexcept-specifiers of friend functions shouldn't need to be
complete-class contexts, but 10.3 doesn't make that distinction that I
can see.
> This was a huge relief because
> member friend function declarations can be redeclared, so we'd have to make
> sure to check if their noexcept-specifiers match. But member function decls
> can't be redeclared. I updated the comment to better reflect why what I'm
> doing there is correct, along with an assert.
But then why do you still need this:
> + /* We can't compare unparsed noexcept-specifiers. Save the decl
> + and check this again after we've parsed the noexcept-specifiers
> + for real. */
> + if (UNPARSED_NOEXCEPT_SPEC_P (new_exceptions))
> + {
> + DEFARG_DECL (TREE_PURPOSE (new_exceptions)) = copy_decl (old_decl);
> + return;
> + }
?
Jason
next prev parent reply other threads:[~2019-06-12 3:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-19 20:27 Marek Polacek
2019-01-04 14:45 ` Marek Polacek
2019-01-07 15:44 ` Jason Merrill
2019-05-10 19:21 ` Marek Polacek
2019-05-17 14:35 ` Marek Polacek
2019-05-24 16:17 ` Marek Polacek
2019-05-28 15:48 ` Jason Merrill
2019-06-04 1:02 ` Marek Polacek
2019-06-10 12:28 ` Marek Polacek
2019-06-12 3:46 ` Jason Merrill [this message]
2019-06-14 20:54 ` Marek Polacek
2019-06-21 20:47 ` Jason Merrill
2019-06-21 21:30 ` Marek Polacek
2019-06-22 0:28 ` Jason Merrill
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=6949597a-e84c-4b87-ec57-f0186b936101@redhat.com \
--to=jason@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=polacek@redhat.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).