public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
* What about supporting std::numeric_limits, std::make_unsigned_t and std::integral concepts as an extension for __uint128_t and __int128_t??
@ 2020-05-23 20:56 sotrdg sotrdg
  2020-05-23 21:26 ` Marc Glisse
  2020-05-23 22:12 ` Jonathan Wakely
  0 siblings, 2 replies; 3+ messages in thread
From: sotrdg sotrdg @ 2020-05-23 20:56 UTC (permalink / raw)
  To: libstdc++

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>);


Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: What about supporting std::numeric_limits, std::make_unsigned_t and std::integral concepts as an extension for __uint128_t and __int128_t??
  2020-05-23 20:56 What about supporting std::numeric_limits, std::make_unsigned_t and std::integral concepts as an extension for __uint128_t and __int128_t?? sotrdg sotrdg
@ 2020-05-23 21:26 ` Marc Glisse
  2020-05-23 22:12 ` Jonathan Wakely
  1 sibling, 0 replies; 3+ messages in thread
From: Marc Glisse @ 2020-05-23 21:26 UTC (permalink / raw)
  To: sotrdg sotrdg; +Cc: libstdc++

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: What about supporting std::numeric_limits, std::make_unsigned_t and std::integral concepts as an extension for __uint128_t and __int128_t??
  2020-05-23 20:56 What about supporting std::numeric_limits, std::make_unsigned_t and std::integral concepts as an extension for __uint128_t and __int128_t?? sotrdg sotrdg
  2020-05-23 21:26 ` Marc Glisse
@ 2020-05-23 22:12 ` Jonathan Wakely
  1 sibling, 0 replies; 3+ messages in thread
From: Jonathan Wakely @ 2020-05-23 22:12 UTC (permalink / raw)
  To: sotrdg sotrdg; +Cc: libstdc++

On Sat, 23 May 2020 at 22:02, sotrdg sotrdg via Libstdc++
<libstdc++@gcc.gnu.org> 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>);

They work with -std=gnu++NN options, but not with -std=c++NN options.

If you want to use non-standard extensions, us the gnu++ modes.

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2020-05-23 22:12 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-05-23 20:56 What about supporting std::numeric_limits, std::make_unsigned_t and std::integral concepts as an extension for __uint128_t and __int128_t?? sotrdg sotrdg
2020-05-23 21:26 ` Marc Glisse
2020-05-23 22:12 ` Jonathan Wakely

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).