public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely@redhat.com>
To: Ville Voutilainen <ville.voutilainen@gmail.com>
Cc: libstdc++ <libstdc++@gcc.gnu.org>
Subject: Re: [RFC] Deprecate non-standard constructors in std::pair
Date: Wed, 7 Apr 2021 13:46:54 +0100	[thread overview]
Message-ID: <20210407124654.GZ3008@redhat.com> (raw)
In-Reply-To: <CAFk2RUZiXUsoO0bEhq6uhPJR9sSq0DXRk5OrQ3jSUotOFgWb=w@mail.gmail.com>

On 07/04/21 15:41 +0300, Ville Voutilainen via Libstdc++ wrote:
>On Wed, 7 Apr 2021 at 15:31, Jonathan Wakely via Libstdc++
><libstdc++@gcc.gnu.org> wrote:
>> I propose that we deprecate the constructors for C++11/14/17/20 in
>> stage 1, and do not support them at all in C++23 mode once P1951 is
>> supported. I have a patch which I'll send in stage 1 (it also uses
>> C++20 concepts to simplify std::pair and fix PR 97930).
>>
>> After a period of deprecation we could remove them, and support P1951
>> for -std=gnu++11/14/17/20 too so that {} continues to work.
>
>The proposal sounds good to me.

Thanks. I've created https://gcc.gnu.org/PR99957 so I don't forget.



  reply	other threads:[~2021-04-07 12:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-07 12:30 Jonathan Wakely
2021-04-07 12:41 ` Ville Voutilainen
2021-04-07 12:46   ` Jonathan Wakely [this message]
2021-04-07 16:59     ` Jonathan Wakely
2021-04-07 17:18       ` Jonathan Wakely
2021-04-28 16:57         ` Jonathan Wakely
2021-04-28 17:19           ` Jonathan Wakely
2021-04-07 18:00       ` Jonathan Wakely
2021-04-07 18:17         ` Jonathan Wakely
2021-04-07 18:25           ` Ville Voutilainen
2021-04-07 18:26             ` Ville Voutilainen
2021-04-28 16:57       ` Jonathan Wakely
2021-04-28 17:00         ` Jonathan Wakely
2021-04-28 17:11           ` Jonathan Wakely

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=20210407124654.GZ3008@redhat.com \
    --to=jwakely@redhat.com \
    --cc=libstdc++@gcc.gnu.org \
    --cc=ville.voutilainen@gmail.com \
    /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).