From: Marc Glisse <marc.glisse@inria.fr>
To: Ken Matsui <kmatsui@cs.washington.edu>
Cc: gcc@gcc.gnu.org, libstdc++ <libstdc++@gcc.gnu.org>
Subject: Re: [GSoC] Conflicted Built-in Trait Name
Date: Sat, 25 Mar 2023 13:38:24 +0100 (CET) [thread overview]
Message-ID: <7f83711f-5094-6c6d-822b-966293062afc@inria.fr> (raw)
In-Reply-To: <CAML+3pVGEV0rdk=+w9x0e+uneJrfkiTj+9kAD+-uf7F6YLA6UQ@mail.gmail.com>
On Sat, 25 Mar 2023, Ken Matsui via Gcc wrote:
> Built-in trait naming simply adds two underscores (__) to the original
> trait name. However, the same names are already in use for some
> built-in traits, such as is_void, is_pointer, and is_signed.
>
> For example, __is_void is used in the following files:
>
> * gcc/testsuite/g++.dg/tm/pr46567.C
This is a testcase, you can rename __is_void to whatever in there, it
doesn't matter.
> * libstdc++-v3/include/bits/cpp_type_traits.h
This __is_void seems to be used in a single place in
include/debug/helper_functions.h, couldn't we tweak that code so __is_void
becomes unused and can be removed?
--
Marc Glisse
next prev parent reply other threads:[~2023-03-25 12:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-25 7:53 Ken Matsui
2023-03-25 12:23 ` Roy Jacobson
2023-03-27 21:58 ` Jonathan Wakely
2023-03-27 22:48 ` Ken Matsui
2023-03-25 12:38 ` Marc Glisse [this message]
2023-03-26 2:01 ` Ken Matsui
2023-03-27 17:33 ` François Dumont
2023-03-27 20:16 ` Ken Matsui
2023-03-27 21:43 ` Jonathan Wakely
2023-03-27 21:49 ` Jonathan Wakely
2023-03-27 21:55 ` Ken Matsui
2023-03-28 21:29 ` Ken Matsui
2023-03-28 23:24 ` Jonathan Wakely
2023-03-28 23:33 ` Ken Matsui
2023-03-30 5:11 ` François Dumont
2023-03-30 8:33 ` Ken Matsui
2023-03-30 12:23 ` Jonathan Wakely
2023-03-30 18:44 ` Ken Matsui
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=7f83711f-5094-6c6d-822b-966293062afc@inria.fr \
--to=marc.glisse@inria.fr \
--cc=gcc@gcc.gnu.org \
--cc=kmatsui@cs.washington.edu \
--cc=libstdc++@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).