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 c++/107600] New __is_destructible built-in
Date: Thu, 10 Nov 2022 03:30:44 +0000	[thread overview]
Message-ID: <bug-107600-4-Ps4QmCn7XA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107600-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107600

--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
I committed r13-3870-g0cbb756fe9c8e1 to speed up the std::destructible concept,
so an intrinsic is not urgent. But it would probably be even better than the
new implementation, and would also help other parts of the lib that use the
trait rather than the concept, such as std::optional and std::variant.

      parent reply	other threads:[~2022-11-10  3:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-10  1:04 [Bug c++/107600] New: " redi at gcc dot gnu.org
2022-11-10  1:07 ` [Bug c++/107600] " redi at gcc dot gnu.org
2022-11-10  1:08 ` mpolacek at gcc dot gnu.org
2022-11-10  3:30 ` redi at gcc dot gnu.org [this message]

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-107600-4-Ps4QmCn7XA@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).