220 27022 <c216cbee-fbfd-ca12-4008-a1fb7d3315e2@f2.dion.ne.jp> article
Path: news.gmane.org!not-for-mail
From: Kazutoshi Satoda <k_satoda@f2.dion.ne.jp>
Newsgroups: gmane.comp.lang.c++.isocpp.proposals
Subject: Re: Better name for std::launder() ?
Date: Fri, 15 Jul 2016 10:42:44 +0900
Lines: 69
Approved: news@gmane.org
Message-ID: <c216cbee-fbfd-ca12-4008-a1fb7d3315e2@f2.dion.ne.jp>
References: <1cd5895f-df27-9cda-73cf-cbc2f1488a2c@f2.dion.ne.jp>
 <CAOfiQq=4m1yiHj2J4fFBdEVwGyS2eMY7-buNRmDdMzyx3QuYag@mail.gmail.com>
Reply-To: std-proposals@isocpp.org
NNTP-Posting-Host: plane.gmane.org
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Trace: ger.gmane.org 1468546990 24558 80.91.229.3 (15 Jul 2016 01:43:10 GMT)
X-Complaints-To: usenet@ger.gmane.org
NNTP-Posting-Date: Fri, 15 Jul 2016 01:43:10 +0000 (UTC)
To: std-proposals@isocpp.org
Original-X-From: std-proposals+bncBDIYVAE3UECRBH77UC6AKGQECN6RDIY@isocpp.org Fri Jul 15 03:42:57 2016
Return-path: <std-proposals+bncBDIYVAE3UECRBH77UC6AKGQECN6RDIY@isocpp.org>
Envelope-to: gclcip-std-proposals@m.gmane.org
Original-Received: from mail-pa0-f72.google.com ([209.85.220.72])
	by plane.gmane.org with esmtp (Exim 4.69)
	(envelope-from <std-proposals+bncBDIYVAE3UECRBH77UC6AKGQECN6RDIY@isocpp.org>)
	id 1bNs9Z-0002Iv-AU
	for gclcip-std-proposals@m.gmane.org; Fri, 15 Jul 2016 03:42:57 +0200
Original-Received: by mail-pa0-f72.google.com with SMTP id q2sf162153084pap.1
        for <gclcip-std-proposals@m.gmane.org>; Thu, 14 Jul 2016 18:42:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=isocpp-org.20150623.gappssmtp.com; s=20150623;
        h=subject:to:references:from:message-id:date:user-agent:mime-version
         :in-reply-to:content-transfer-encoding:x-original-sender
         :x-original-authentication-results:reply-to:precedence:mailing-list
         :list-id:x-spam-checked-in-group:list-post:list-help:list-archive
         :list-subscribe:list-unsubscribe;
        bh=fGRROFqwZHxJlHQmwJqkwczKYpCVo/KtSOnt9MVlek0=;
        b=Tbke0tsajWfCosuFv6bHu6nuFKlBjeKxdtbLsaam4xbnXDQ6rj+58Fym1obS1mTnCD
         fV/6aSgrAPoYiG7uNQiXJxYF4kkL7ZumOH+YF9KvsQnNrGL4++09ju9sa5bTceFMERU+
         JdW42930h1UbqGd4r+3xl9Ib5OPC5Cn6bozbjD0daOHrEhoJ+PuOQdjVPE+gg+JMtlr5
         hz0on6SP/UNbLGF/PUGLCXS8ildax+Y+Tmqo36fF3tZSWH78YnnGeNVwYpSvcZNfXjhN
         HFkknhp09exlIrpv79qZz6MLXEIIElSOzkIcGB95lUnQTS7It8ddWnzfjSkvTfYxn4dm
      
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20130820;
        h=x-gm-message-state:subject:to:references:from:message-id:date
         :user-agent:mime-version:in-reply-to:content-transfer-encoding
         :x-original-sender:x-original-authentication-results:reply-to
         :precedence:mailing-list:list-id:x-spam-checked-in-group:list-post
         :list-help:list-archive:list-subscribe:list-unsubscribe;
        bh=fGRROFqwZHxJlHQmwJqkwczKYpCVo/KtSOnt9MVlek0=;
        b=L+hRC/OzZqMfSTI39yajR7jdmZUu4vYJxvk0nmQ+q0Mumzdv8BdZcfyv6VuVjNC7Pd
         iOuJq0NznGBd+SwdhDZuI6hWy0NR3MyX8hTDCWzbb8jAubo0hxXSWHSghbIPlCmrFYa2
         Elao+SFnLz9dWYec9OoVjgxn1gdr3PHeGhmqagZlkgD08EZ+rE9CNG6xJ7zDpkCyPBQr
         rzNvjxbn9ZinIQBUpsCmt87G163AnpEZbkHS5LAt6OHqD5IrBYNbnxMJxHzD7XukTBIX
         +s6S00W04C1ys0FBfk3+FF8w+CaJdCHDsBSj/7UxaiSKPGGEgk8LA83mRCWYLp62Y/QW
  
X-Gm-Message-State: ALyK8tKPr4LW+H5VxtNwTybcpwwJIu8FF+yvYxeMZyz1X9cXBQpEx7dIdzYVDVOUNWH1PA==
X-Received: by 10.98.23.84 with SMTP id 81mr8615464pfx.7.1468546976369;
        Thu, 14 Jul 2016 18:42:56 -0700 (PDT)
X-BeenThere: std-proposals@isocpp.org
Original-Received: by 10.36.53.141 with SMTP id k135ls76982ita.13.canary; Thu, 14 Jul
 2016 18:42:55 -0700 (PDT)
X-Received: by 10.107.131.11 with SMTP id f11mr18532471iod.136.1468546975478;
        Thu, 14 Jul 2016 18:42:55 -0700 (PDT)
Original-Received: from dmta02.auone-net.jp (mail-ae0-f57.auone-net.jp. [106.187.230.57])
        by mx.google.com with ESMTP id v102si6173006ioi.6.2016.07.14.18.42.55
        for <std-proposals@isocpp.org>;
        Thu, 14 Jul 2016 18:42:55 -0700 (PDT)
Received-SPF: pass (google.com: domain of k_satoda@f2.dion.ne.jp designates 106.187.230.57 as permitted sender) client-ip=106.187.230.57;
Original-Received: from amlmta402.auone-net.jp (amlmta402-MM [10.188.23.193])
	by dmta02.auone-net.jp (au one net mail) with ESMTP id 7784940051A
	for <std-proposals@isocpp.org>; Fri, 15 Jul 2016 10:42:54 +0900 (JST)
Original-Received: from [0.0.0.0] ([51.255.33.0])
	by amlmta402.auone-net.jp id 57883f9c000d872b00002dde00002ffb380004927f94;
	Fri, 15 Jul 2016 10:42:52 +0900
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101
 Thunderbird/45.2.0
In-Reply-To: <CAOfiQq=4m1yiHj2J4fFBdEVwGyS2eMY7-buNRmDdMzyx3QuYag@mail.gmail.com>
X-MXM-DELIVERY-TYPE: 3
X-Original-Sender: k_satoda@f2.dion.ne.jp
X-Original-Authentication-Results: mx.google.com;       spf=pass (google.com:
 domain of k_satoda@f2.dion.ne.jp designates 106.187.230.57 as permitted
 sender) smtp.mailfrom=k_satoda@f2.dion.ne.jp
Precedence: list
Mailing-list: list std-proposals@isocpp.org; contact std-proposals+owners@isocpp.org
List-ID: <std-proposals.isocpp.org>
X-Spam-Checked-In-Group: std-proposals@isocpp.org
X-Google-Group-Id: 399137483710
List-Post: <https://groups.google.com/a/isocpp.org/group/std-proposals/post>, <mailto:std-proposals@isocpp.org>
List-Help: <https://support.google.com/a/isocpp.org/bin/topic.py?topic=25838>, <mailto:std-proposals+help@isocpp.org>
List-Archive: <https://groups.google.com/a/isocpp.org/group/std-proposals/>
List-Subscribe: <https://groups.google.com/a/isocpp.org/group/std-proposals/subscribe>,
 <mailto:std-proposals+subscribe@isocpp.org>
List-Unsubscribe: <mailto:googlegroups-manage+399137483710+unsubscribe@googlegroups.com>,
 <https://groups.google.com/a/isocpp.org/group/std-proposals/subscribe>
Xref: news.gmane.org gmane.comp.lang.c++.isocpp.proposals:27022
Archived-At: <http://permalink.gmane.org/gmane.comp.lang.c++.isocpp.proposals/27022>

On 2016/07/14 3:47 +0900, Richard Smith wrote:
> On Wed, Jul 13, 2016 at 11:24 AM, Kazutoshi Satoda <k_satoda@f2.dion.ne.j=
p>
> wrote:
....
>> It could be std::suppose_new_at_reused_storage(), as a strawman. The
>> example at [ptr.launder] would look like this:
>>
>>   struct X { const int n; };
>>   X *p =3D new X{3};
>>   const int a =3D p->n;
>>   new (p) X{5}; // p does not point to new object (3.8)
>>                 // because X::n is const
>>   const int b =3D p->n; // undefined behavior
>>   const int c =3D std::suppose_new_at_reused_storage(p)->n; // OK
>>
>>
>> What do you think? Is it too late?
>=20
> If you file a national body comment on the CD ballot suggesting renaming
> it, along with a proposed new name and rationale, it's not too late for t=
he
> committee to consider a different name.
>
>> Does someone know the history of the naming?
>=20
> The current name was originally suggested as -- essentially -- a
> placeholder name, albeit a plausible one, and seems to have broadly been
> considered good enough to not require changing. LEWG review discussed the
> name and decided unanimously that they were fine with it as-is. CWG revie=
w
> also discussed the name briefly and did not propose changing it.

Hearing its history, with no strong rationales, I still think renaming it
is appropriate. I'll try to send a national body comment.

Thank you and those who suggested other (some funny) alternatives.

For now, I still think std::suppose_new_at_reused_storage() is the best.
"suppose" stands for possibility of cases when the original object is
still there. "new" stands to indicate lifetime issues by the well known
keyword. "reused storage" stands to indicate the issue is about reusing
the storage manually. And there is no need to shorten the name.

However, more suggestions are welcome, of course.


FYI, I found a related note about the name in a report of Kona meeting
by Jonathan Wakely, which can be an additional motivation to rename it.
> ... After the meeting it was pointed out that some industries might have
> trouble convincing regulators that =E2=80=98launder=E2=80=99 is an approp=
riate
> identifier to have in their code. (A similar objection was raised to the
> function corrupted_by_exception ...). ...
http://accu.org/var/uploads/journals/CVu281-78ac.pdf

--=20
k_satoda

--=20
You received this message because you are subscribed to the Google Groups "=
ISO C++ Standard - Future Proposals" group.
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to std-proposals+unsubscribe@isocpp.org.
To post to this group, send email to std-proposals@isocpp.org.
To view this discussion on the web visit https://groups.google.com/a/isocpp=
..org/d/msgid/std-proposals/c216cbee-fbfd-ca12-4008-a1fb7d3315e2%40f2.dion.n=
e.jp.

.
