From: Marc Glisse <marc.glisse@inria.fr>
To: sotrdg sotrdg <euloanty@live.com>
Cc: libstdc++ <libstdc++@gcc.gnu.org>
Subject: Re: What about supporting std::numeric_limits, std::make_unsigned_t and std::integral concepts as an extension for __uint128_t and __int128_t??
Date: Sat, 23 May 2020 23:26:28 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2005232325270.7372@stedding.saclay.inria.fr> (raw)
In-Reply-To: <CH2PR02MB652214B53F50612D95AF2F19B2B50@CH2PR02MB6522.namprd02.prod.outlook.com>
On Sat, 23 May 2020, sotrdg sotrdg via Libstdc++ wrote:
> It is absolutely a pain in a template world code like this do not work.
>
> std::make_unsigned_t<__int128_t>;
> static_assert(std::unsigned_integral<__uint128_t>);
Aren't most of those already supported? What exact code are you compiling
with what exact compiler and options?
--
Marc Glisse
next prev parent reply other threads:[~2020-05-23 21:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-23 20:56 sotrdg sotrdg
2020-05-23 21:26 ` Marc Glisse [this message]
2020-05-23 22:12 ` Jonathan Wakely
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=alpine.DEB.2.22.394.2005232325270.7372@stedding.saclay.inria.fr \
--to=marc.glisse@inria.fr \
--cc=euloanty@live.com \
--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).