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 libstdc++/24537] Non-uglified names inside namespace __gnu_cxx
Date: Fri, 04 Nov 2022 19:20:29 +0000 [thread overview]
Message-ID: <bug-24537-4-ZFbB80nytr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-24537-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=24537
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |WAITING
--- Comment #8 from Jonathan Wakely <redi at gcc dot gnu.org> ---
I would like to suggest closing this bug. I don't think we should rename
__gnu_cxx::char_traits, it uses a reserved name. I don't think there is
anything wrong with e.g. __debug::vector or __gnu_cxx::char_traits and we
shouldn't pick ugly names to avoid problems for users who abuse
using-directives.
Changing status to WAITING to start the timer, but if I don't hear otherwise
then I'll close it.
next parent reply other threads:[~2022-11-04 19:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-24537-4@http.gcc.gnu.org/bugzilla/>
2022-11-04 19:20 ` redi at gcc dot gnu.org [this message]
2005-10-26 10:28 [Bug libstdc++/24537] New: " pcarlini at suse dot de
2005-10-26 12:34 ` [Bug libstdc++/24537] " pinskia at gcc dot gnu dot org
2005-10-26 12:37 ` pcarlini at suse dot de
2005-10-27 6:04 ` bkoz at gcc dot gnu dot org
2005-10-27 9:07 ` pcarlini at suse dot de
2005-10-27 21:55 ` pinskia at gcc dot gnu dot org
2006-11-21 10:48 ` bkoz at gcc dot gnu dot 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-24537-4-ZFbB80nytr@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).