From: Jason Merrill <jason@redhat.com>
To: Martin Sebor <msebor@gmail.com>
Cc: Gcc Patch List <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] document cp_operator_id and cp_assignment_operator_id
Date: Thu, 15 Jun 2017 21:25:00 -0000 [thread overview]
Message-ID: <CADzB+2kNyR4zkuC_ZWQqCZJE2a9aK5F0BZ=LaB13eHJahp_O1w@mail.gmail.com> (raw)
In-Reply-To: <620e2b9e-a77e-167d-52e3-0b34efa688a5@gmail.com>
On Thu, Jun 15, 2017 at 12:57 PM, Martin Sebor <msebor@gmail.com> wrote:
> Attached is a documentation-only change to add comments explaining
> the C++ cp_operator_id and cp_assignment_operator_id macros.
Hmm, I'd say that these macros return the identifier used internally
to represent "operator OP" and "operator OP=", respectively. Looking
up overloads is one thing you can do with that name, but the same is
true of all identifiers, do we need to mention it specifically?
Jason
next prev parent reply other threads:[~2017-06-15 21:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-15 16:57 Martin Sebor
2017-06-15 21:25 ` Jason Merrill [this message]
2017-06-15 22:57 ` Martin Sebor
2017-07-01 21:42 ` 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='CADzB+2kNyR4zkuC_ZWQqCZJE2a9aK5F0BZ=LaB13eHJahp_O1w@mail.gmail.com' \
--to=jason@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=msebor@gmail.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).