public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ensadc at mailnesia dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/105505] New: P1951R1 (Default Arguments for pair's Forwarding Constructor) is unimplemented
Date: Fri, 06 May 2022 14:48:56 +0000	[thread overview]
Message-ID: <bug-105505-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 105505
           Summary: P1951R1 (Default Arguments for pair's Forwarding
                    Constructor) is unimplemented
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: ensadc at mailnesia dot com
                CC: redi at gcc dot gnu.org
  Target Milestone: ---

https://en.cppreference.com/w/cpp/compiler_support claims that P1951R1 (Default
Arguments for pair's Forwarding Constructor) is supported in GCC libstdc++ 12,
but it seems that libstdc++ 12 doesn't actually add default template arguments
for said forwarding constructor.

For example, the following still does not work with libstdc++ (but works with
latest libc++ and MSVC STL: https://godbolt.org/z/6oY3G77oT).

```
#include <utility>

struct MoveOnly {
    MoveOnly();
    MoveOnly(MoveOnly&&);
};

std::pair<int, MoveOnly> p{42, {}};
```

             reply	other threads:[~2022-05-06 14:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-06 14:48 ensadc at mailnesia dot com [this message]
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
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@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).