public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/96537] Missing std::pair constructor
Date: Mon, 10 Aug 2020 10:34:27 +0000	[thread overview]
Message-ID: <bug-96537-4-S4cqotfkYu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96537-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #2)
> Not a bug. C++11 and C++14 said for the relevant pair(U&&, V&&) constructor:
> 
> Remarks: If U is not implicitly convertible to first_type or V is not
> implicitly convertible to second_type this constructor shall not participate
> in overload resolution.
> 
> That was changed for C++17 by http://wg21.link/n4387 which was accepted into
> the C++17 draft in 2015, so you can't expect C++11 compilers released before
> then to support the new API.

Thanks for the comment.  Still, if this is a language version issue, I used
-std=c++11 with 7.5.0, shouldn't I then get the same behaviour as with gcc
4.8.5?

  parent reply	other threads:[~2020-08-10 10:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-08 16:05 [Bug c++/96537] New: " vries at gcc dot gnu.org
2020-08-08 16:08 ` [Bug c++/96537] " vries at gcc dot gnu.org
2020-08-10 10:30 ` redi at gcc dot gnu.org
2020-08-10 10:31 ` redi at gcc dot gnu.org
2020-08-10 10:34 ` vries at gcc dot gnu.org [this message]
2020-08-10 10:34 ` redi at gcc dot gnu.org
2020-08-10 10:36 ` redi at gcc dot gnu.org
2020-08-10 10:36 ` 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-96537-4-S4cqotfkYu@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).