From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <jwakely@redhat.com>
Received: from us-smtp-delivery-124.mimecast.com
 (us-smtp-delivery-124.mimecast.com [170.10.133.124])
 by sourceware.org (Postfix) with ESMTP id 9FBD13858028
 for <libstdc++@gcc.gnu.org>; Wed,  7 Apr 2021 12:46:59 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 9FBD13858028
Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com
 [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id
 us-mta-90-EMog06HkP3i9tCZLc9bzAw-1; Wed, 07 Apr 2021 08:46:56 -0400
X-MC-Unique: EMog06HkP3i9tCZLc9bzAw-1
Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com
 [10.5.11.14])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 6A987807918;
 Wed,  7 Apr 2021 12:46:55 +0000 (UTC)
Received: from localhost (unknown [10.33.36.164])
 by smtp.corp.redhat.com (Postfix) with ESMTP id 0BC375D9CA;
 Wed,  7 Apr 2021 12:46:54 +0000 (UTC)
Date: Wed, 7 Apr 2021 13:46:54 +0100
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
Message-ID: <20210407124654.GZ3008@redhat.com>
References: <20210407123050.GY3008@redhat.com>
 <CAFk2RUZiXUsoO0bEhq6uhPJR9sSq0DXRk5OrQ3jSUotOFgWb=w@mail.gmail.com>
MIME-Version: 1.0
In-Reply-To: <CAFk2RUZiXUsoO0bEhq6uhPJR9sSq0DXRk5OrQ3jSUotOFgWb=w@mail.gmail.com>
X-Clacks-Overhead: GNU Terry Pratchett
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.14
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Disposition: inline
X-Spam-Status: No, score=-8.0 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH,
 DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, KAM_SHORT,
 RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H4, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE,
 SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
 server2.sourceware.org
X-BeenThere: libstdc++@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Libstdc++ mailing list <libstdc++.gcc.gnu.org>
List-Unsubscribe: <https://gcc.gnu.org/mailman/options/libstdc++>,
 <mailto:libstdc++-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/libstdc++/>
List-Post: <mailto:libstdc++@gcc.gnu.org>
List-Help: <mailto:libstdc++-request@gcc.gnu.org?subject=help>
List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/libstdc++>,
 <mailto:libstdc++-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Apr 2021 12:47:00 -0000

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.