public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hewillk at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/101739] Some function parameters in <ranges> missing uglify
Date: Tue, 31 Aug 2021 17:20:44 +0000 [thread overview]
Message-ID: <bug-101739-4-HxfHkmqix6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101739-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101739
--- Comment #2 from 康桓瑋 <hewillk at gmail dot com> ---
(In reply to Jonathan Wakely from comment #1)
> These changes are not strictly necessary.
>
> "base" is a reserved name, because of move_iterator::base() etc.
>
> and "i" is a reserved name, because of operator""i() in <complex>.
>
> So users cannot define those as macros, and so it's safe for us to use them.
Extremely reasonable.
next prev parent reply other threads:[~2021-08-31 17:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-03 6:32 [Bug libstdc++/101739] New: " hewillk at gmail dot com
2021-08-31 17:05 ` [Bug libstdc++/101739] " redi at gcc dot gnu.org
2021-08-31 17:20 ` hewillk at gmail dot com [this message]
2021-08-31 18:24 ` redi at gcc dot gnu.org
2021-09-01 11:52 ` hewillk at gmail dot com
2021-09-01 12:32 ` redi at gcc dot gnu.org
2023-04-12 16:17 ` ppalka 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-101739-4-HxfHkmqix6@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).