public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/104477] New: [C++23] Implement P2255R2, type trait to detect reference binding to temporary
Date: Wed, 09 Feb 2022 19:46:36 +0000	[thread overview]
Message-ID: <bug-104477-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 104477
           Summary: [C++23] Implement P2255R2, type trait to detect
                    reference binding to temporary
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: jason at gcc dot gnu.org
  Target Milestone: ---

http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2021/p2255r2.html

The library type traits std::reference_{constructs,converts}_from_temporary
will need a compiler intrinsic to implement.

Apparently clang already has a __reference_binds_to_temporary with similar but
not identical semantics; I think let's see if they plan to adjust that builtin
or add a new one before we settle on a name.

             reply	other threads:[~2022-02-09 19:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-09 19:46 jason at gcc dot gnu.org [this message]
2022-02-09 19:47 ` [Bug c++/104477] " jason at gcc dot gnu.org
2022-05-27 15:04 ` mpolacek at gcc dot gnu.org
2022-05-27 15:24 ` jakub at gcc dot gnu.org
2022-06-29 23:20 ` mpolacek at gcc dot gnu.org
2022-06-29 23:23 ` pinskia at gcc dot gnu.org
2022-07-01 11:27 ` redi at gcc dot gnu.org
2022-07-15 15:33 ` cvs-commit at gcc dot gnu.org
2022-07-15 15:35 ` mpolacek at gcc dot gnu.org

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