public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paolo.carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/52702] [C++11] std::is_trivially_destructible is missing
Date: Sun, 15 Apr 2012 17:05:00 -0000	[thread overview]
Message-ID: <bug-52702-4-ZYPYQ1eRtb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52702-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52702

Paolo Carlini <paolo.carlini at oracle dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jason at gcc dot gnu.org

--- Comment #5 from Paolo Carlini <paolo.carlini at oracle dot com> 2012-04-15 17:05:18 UTC ---
Maybe we can ask here Jason about std::is_trivially_copyable, which he didn't
do at once with std::is_trivial (maybe the concept didn't precisely exist at
the time, I don't remember).

Anyway, I see two options: either "exporting" just now from the front-end an
__is_trivially_copyable (just using trivially_copyable_p); or postpone the task
to when std::is_trivially_constructible and std::is_trivially_assignable will
be available, in turn requiring front-end support, but then useful for all the
missing std::is_trivial* things, if I understand correctly.

The former could make sense per se, could also be immediately exploited to
implement std::is_trivially_default_constructible. At some point, anyway, we'll
have to tackle std::is_trivially_constructible and std::is_trivially_assignable
(the former, in particular, with its variadic parameter, seems non-trivial to
me)


  parent reply	other threads:[~2012-04-15 17:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-24 17:44 [Bug libstdc++/52702] New: " daniel.kruegler at googlemail dot com
2012-04-12 12:22 ` [Bug libstdc++/52702] " paolo.carlini at oracle dot com
2012-04-15 13:44 ` paolo.carlini at oracle dot com
2012-04-15 14:06 ` daniel.kruegler at googlemail dot com
2012-04-15 14:30 ` paolo.carlini at oracle dot com
2012-04-15 17:05 ` paolo.carlini at oracle dot com [this message]
2012-04-15 17:48 ` paolo.carlini at oracle dot com
2012-04-15 23:35 ` paolo at gcc dot gnu.org
2012-04-22  8:06 ` paolo.carlini at oracle dot com

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-52702-4-ZYPYQ1eRtb@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).