public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/105505] P1951R1 (Default Arguments for pair's Forwarding Constructor) is unimplemented
Date: Fri, 12 Jan 2024 09:48:21 +0000	[thread overview]
Message-ID: <bug-105505-4-lPU4YH54Sb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105505-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>:

https://gcc.gnu.org/g:35f8c661d67f53486f2f3e25887323476a7d0c2b

commit r14-7173-g35f8c661d67f53486f2f3e25887323476a7d0c2b
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Thu Jan 11 22:38:02 2024 +0000

    libstdc++: Implement C++23 P1951R1 (Default Args for pair's Forwarding
Ctor) [PR105505]

    This was approved for C++23 at he June 2021 virtual meeting.

    This allows more efficient construction of std::pair members when {} is
    used as a constructor argument. The perfect forwarding constructor can
    be used, so that the member variables are constructed from forwarded
    arguments instead of being copy constructed from temporaries.

    libstdc++-v3/ChangeLog:

            PR libstdc++/105505
            * include/bits/stl_pair.h (pair::pair(U1&&, U2&&)) [C++23]: Add
            default template arguments, as per P1951R1.
            * testsuite/20_util/pair/cons/default_tmpl_args.cc: New test.

  parent reply	other threads:[~2024-01-12  9:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-06 14:48 [Bug libstdc++/105505] New: " ensadc at mailnesia dot com
2022-05-06 17:11 ` [Bug libstdc++/105505] " redi at gcc dot gnu.org
2022-09-29 18:11 ` redi at gcc dot gnu.org
2024-01-11 22:51 ` redi at gcc dot gnu.org
2024-01-12  9:48 ` cvs-commit at gcc dot gnu.org [this message]
2024-01-12 20:39 ` redi 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-105505-4-lPU4YH54Sb@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).