220 26913 <293092d0-26d8-4414-9e23-bfa6a4638d88@isocpp.org> article Path: news.gmane.org!not-for-mail From: Nicol Bolas Newsgroups: gmane.comp.lang.c++.isocpp.proposals Subject: Re: Better name for std::launder() ? Date: Wed, 13 Jul 2016 14:35:28 -0700 (PDT) Lines: 88 Approved: news@gmane.org Message-ID: <293092d0-26d8-4414-9e23-bfa6a4638d88@isocpp.org> References: <1cd5895f-df27-9cda-73cf-cbc2f1488a2c@f2.dion.ne.jp> Reply-To: std-proposals@isocpp.org NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_9_841736937.1468445728340" X-Trace: ger.gmane.org 1468445742 30652 80.91.229.3 (13 Jul 2016 21:35:42 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 13 Jul 2016 21:35:42 +0000 (UTC) Cc: richard@metafoo.co.uk To: ISO C++ Standard - Future Proposals Original-X-From: std-proposals+bncBCEKFTV6ZUMBBIPITK6AKGQEHBBAM4Y@isocpp.org Wed Jul 13 23:35:36 2016 Return-path: Envelope-to: gclcip-std-proposals@m.gmane.org Original-Received: from mail-pf0-f197.google.com ([209.85.192.197]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1bNRoZ-0005IR-V9 for gclcip-std-proposals@m.gmane.org; Wed, 13 Jul 2016 23:35:32 +0200 Original-Received: by mail-pf0-f197.google.com with SMTP id y134sf63965095pfg.1 for ; Wed, 13 Jul 2016 14:35:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isocpp-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:message-id:in-reply-to:references:subject :mime-version:x-original-sender:reply-to:precedence:mailing-list :list-id:x-spam-checked-in-group:list-post:list-help:list-archive :list-subscribe:list-unsubscribe; bh=Zn1fLMNg0ocJvo1BGo0bHX5QuI2kmVNqkM20SeKfBx0=; b=sQklGcVdqnlBpf/dCClcnGkYmIppIZZAeTpHl/2wF1ETN6RmE7tSP0BeYh1I4b9oSP 6nfaHdUyXgSrndzQM4S9yigh1xo21q/wf2i/tdxgM5N13Zx2TRsoz5Pl7LOsQmj0Xrms 0hHlDBj3TG35nP8siilJv0YzmhRPVbtAC5ip8+MvhTO13+eS6CKs2UEfSj1GaIlShtAM EnP1dNnKsYWvG3RA5rD8HGAk/FTWJLy33Zpu+5/c/pSIWk3PlaMS6AFNofqPE3RyPbEb acxOdFKNbB/OqFC8U13EHZ8cBWAdeMg4ksKYrQ64Ja6BZc2SFmuDTuemYMWvDRtJOvFJ UtNw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:message-id:in-reply-to:references:subject :mime-version:x-original-sender:reply-to:precedence:mailing-list :list-id:x-spam-checked-in-group:list-post:list-help:list-archive :list-subscribe:list-unsubscribe; bh=Zn1fLMNg0ocJvo1BGo0bHX5QuI2kmVNqkM20SeKfBx0=; b=uvF9FJCZRM70/3BesXn83W+2wkAf77mHi2fYmSeQ26h/a3Uta7Gg+0V9CFob7ldeE4 M9zz44PhzZ6EJ7ymYu4RE+IqSpa8tB+2aTSDupb7H5RbPot4VWDdLrPYp2Bj6yhroy+B gNtSiKPNdF/WaMJUNNtMK3h1LNWgiH0RavBl4rbIoCh5ylHnTMMjhvYuTLuvW13prjYE gNfFfvYj61H3nGZHQZkX3/9VZj1z2SnCMWl/0zc3ZKoRZPksnQNKNG86xtnZ7ZNJ3Akj UnOChXTuQF8fJop+ydGbD16brdc4mP96gt5LLrsl6y39q0EZElNyONy+icnAs24G3WUi nung== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:message-id:in-reply-to :references:subject:mime-version:x-original-sender:reply-to :precedence:mailing-list:list-id:x-spam-checked-in-group:list-post :list-help:list-archive:list-subscribe:list-unsubscribe; bh=Zn1fLMNg0ocJvo1BGo0bHX5QuI2kmVNqkM20SeKfBx0=; b=kBEWkSEsNkQL7Q0HEtUe9PjX6P5lyMGx6GsolyiGvTRNRj7FhTvmtIhF6378z8YCEF 7LIuqNWdElviDwEkfroYNCeo7/KUQCm8jjf+9f4+Fuxr1ZVELcW3AbG8DjyameHIOFyq VfV1TlzbVJ0Z5FuNMHCiRlZuDPjUpQpfs7DFIohaLBvn/gPyRLcUwQZKaDYN9c4QqGJs pZ45MU0L19/HXRDyMG3aDEOC+jpghd0UkYf+PCukVd45FWOOUlvMWG3f2w2rkf6IJEyF QfR+SQIHoF7KKJuCOlF5+g5XOH/7SW3iylzZAHmZKTp3i6vcM3pGg4v7h+2TX9KnBICy f5Lg== X-Gm-Message-State: ALyK8tItG7eNPJikeptbNryZxpJKiraTymbN1nqK0hhr73uuMfPJBnEBS9sG4w2qFHPgLQ== X-Received: by 10.66.4.38 with SMTP id h6mr7767332pah.13.1468445730784; Wed, 13 Jul 2016 14:35:30 -0700 (PDT) X-BeenThere: std-proposals@isocpp.org Original-Received: by 10.107.52.5 with SMTP id b5ls79066ioa.9.gmail; Wed, 13 Jul 2016 14:35:29 -0700 (PDT) X-Received: by 10.36.133.10 with SMTP id r10mr792412itd.1.1468445729361; Wed, 13 Jul 2016 14:35:29 -0700 (PDT) In-Reply-To: <1cd5895f-df27-9cda-73cf-cbc2f1488a2c@f2.dion.ne.jp> X-Original-Sender: jmckesson@gmail.com Precedence: list Mailing-list: list std-proposals@isocpp.org; contact std-proposals+owners@isocpp.org List-ID: X-Spam-Checked-In-Group: std-proposals@isocpp.org X-Google-Group-Id: 399137483710 List-Post: , List-Help: , List-Archive: List-Subscribe: , List-Unsubscribe: , Xref: news.gmane.org gmane.comp.lang.c++.isocpp.proposals:26913 Archived-At: ------=_Part_9_841736937.1468445728340 Content-Type: multipart/alternative; boundary="----=_Part_10_169963926.1468445728341" ------=_Part_10_169963926.1468445728341 Content-Type: text/plain; charset=UTF-8 On Wednesday, July 13, 2016 at 2:25:08 PM UTC-4, Kazutoshi SATODA wrote: > > http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2015/p0137r0.html > (accepted for C++17) > > The name std::launder() seems cryptic. There is no hint in the word > "launder" to show it is about the C++ object model, lifetime, and > reusing storage. The situation is likely same even if a programmer > preliminarily knows about the issues it solves. Comments like "Here, > compilers should suppose new object at reused storage" will be wanted > each time it is used. > I appreciate the fact that it's not a very a priori descriptive name. But at the same time, it's a *funny* name. You're taking part in a memory laundering exercise. If I have to look at/write the kind of code that needs to employ this technique, I'd like to get a chuckle out of it ;) Admittedly, it's not a very good defense of the name. -- 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 email 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/293092d0-26d8-4414-9e23-bfa6a4638d88%40isocpp.org. ------=_Part_10_169963926.1468445728341 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Wednesday, July 13, 2016 at 2:25:08 PM UTC-4, Kazutoshi= SATODA wrote:
http://www.open-std.org/= jtc1/sc22/wg21/docs/papers/2015/p0137r0.html
(accepted for C++17)

The name std::launder() seems cryptic. There is no hint in the word
"launder" to show it is about the C++ object model, lifetime,= and
reusing storage. The situation is likely same even if a programmer
preliminarily knows about the issues it solves. Comments like "Her= e,
compilers should suppose new object at reused storage" will be wan= ted
each time it is used.

I appreciate the fact th= at it's not a very a priori descriptive name. But at the same time, it&= #39;s a funny name. You're taking part in a memory laundering ex= ercise.

If I have to look at/write the kind of code that needs to em= ploy this technique, I'd like to get a chuckle out of it ;)

Admi= ttedly, it's not a very good defense of the name.

--
You received this message because you are subscribed to the Google Groups &= quot;ISO C++ Standard - Future Proposals" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to std-proposa= ls+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/293092d0-26d8-4414-9e23-bfa6a4638d88= %40isocpp.org.
------=_Part_10_169963926.1468445728341-- ------=_Part_9_841736937.1468445728340-- .