220 39677 article Path: news.gmane.org!.POSTED!not-for-mail From: florian.csdt@gmail.com Newsgroups: gmane.comp.lang.c++.isocpp.proposals Subject: Re: Thoughts about relocation Date: Fri, 10 Aug 2018 10:19:01 -0700 (PDT) Lines: 98 Approved: news@gmane.org Message-ID: References: <19d8d86c-f4cf-47a9-bb42-9e2ba06dccab@isocpp.org> Reply-To: std-proposals@isocpp.org NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_863_1761433725.1533921541339" X-Trace: blaine.gmane.org 1533921417 28799 195.159.176.226 (10 Aug 2018 17:16:57 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 10 Aug 2018 17:16:57 +0000 (UTC) To: ISO C++ Standard - Future Proposals Original-X-From: std-proposals+bncBC26HM4V3MIRBBUSW7NQKGQE73GSA6I@isocpp.org Fri Aug 10 19:16:53 2018 Return-path: Envelope-to: gclcip-std-proposals@m.gmane.org Original-Received: from mail-yw1-f72.google.com ([209.85.161.72]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1foB1x-0007OO-B5 for gclcip-std-proposals@m.gmane.org; Fri, 10 Aug 2018 19:16:53 +0200 Original-Received: by mail-yw1-f72.google.com with SMTP id 22-v6sf13709908ywd.15 for ; Fri, 10 Aug 2018 10:19:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isocpp-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:message-id:in-reply-to:references:subject:mime-version :x-original-sender:reply-to:precedence:mailing-list:list-id :list-post:list-help:list-archive:list-subscribe:list-unsubscribe; bh=WtveVf6O29DF2hWhADpopQapaRzovJw2hR4YEUmPmTg=; b=q8HX0fyHcaqP6jmXnxkEh87nJQ2iLgVUMKh8yxlWyvpX3lliyAyN49BUowJprmhBvl KJSG56d7rG8A2RgbR/vEQumCtN8+fxFY+gM+Hp0R0/vOwWyU40dVrTHcjkhGZyAFnv9+ De1yRJ3kuzxh4iZGpyob+CumkwGy6hheQMFzQbSEwUkaDEw4GCU/89HntfOz422iUEW0 JB66YSMxnRe2tBjrzvwP/RhSTd6TduqJKlHzm2/6pCRvLYGh/U74yKR8FrdmvVCb4K7d wUXOlFb67D40FN3nV+Ta/0EdRj1trJEEMR5trIjp9Ic0I5XWuTCLKe4+Btkw2pS6NEkk AAng== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:message-id:in-reply-to:references:subject:mime-version :x-original-sender:reply-to:precedence:mailing-list:list-id :list-post:list-help:list-archive:list-subscribe:list-unsubscribe; bh=WtveVf6O29DF2hWhADpopQapaRzovJw2hR4YEUmPmTg=; b=a07ZaE0ZoPaRTuZmbLnreCeMCUc5c/VhZSVMjomxHrtU9DNeEbIvTgCUCmXeRFPuVa fKmjSLJULl/LMWcDySCbBXzksPtLF1rvIS45dp+L5FoUS+fLG278VbMO+Z1QK2Chuw4m w+H/zuDraONqMFnVwB1W1AtR9dLh8ZoHHGkGqJahioeMRyRsw4c8b6so55PYunsrXeI7 QuUOZ43aXF4QV18AGZQUcCGBVhRoV2PGRZZB3x6EqihqGlk13pa4ZeVB4am2a4WgDqUI X7BXODXydYTzXfe0kcOE/Mtqk3qUQpk7/xnhSndF9vdN8wUswaH6EyJA+2PalgsS/bsL Z1rg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to: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=WtveVf6O29DF2hWhADpopQapaRzovJw2hR4YEUmPmTg=; b=CODtp/DVOL1oWOSQ95dGzVUzdywLIBw8V96IkVNCp95hNn4GbQBFwEzz1/RHeywKP5 d+kJuLzudWbXWZJaWF8NBBJ6GJJrERcJTFa8eXYIYwkMsmF4Q60YpktiXdjGExFhAvA6 vkg286L8NJAeEDAcbIebsOxHX2RyxrCSt4sQqsvdsnyGvr103mOFqIZtP9C4LoyoO1ke 1QOyyy7JMS1hRGrKUntpZzEQqy3boLgBN7xw4pMSQxqqmFuYMivVTm+FlzNJNTREMtP2 NHrimqlxLIsGIyUJ/h7eMf/IPE+OVep4p/DR8TDXxCdEt4+VlRfU7XgtwDC2oFBN3vkD 1tVg== X-Gm-Message-State: AOUpUlF6pL0Tahr6vyRKOPbjc6wEcvIzMkpOAKH/+cn4jB1LuWkkus3z fx+He5RZJ5Bogqgpe9JFYsMtMA== X-Google-Smtp-Source: AA+uWPxHmGfHIpxWdOepz+zYeG8rzqVYetwQMfCq2qoWuLZhjmoZhIb2Nj+2WUM3jibPuPZjxdqRTw== X-Received: by 2002:a81:9fd4:: with SMTP id w203-v6mr2319667ywg.161.1533921543467; Fri, 10 Aug 2018 10:19:03 -0700 (PDT) X-BeenThere: std-proposals@isocpp.org Original-Received: by 2002:a81:11d3:: with SMTP id 202-v6ls1923216ywr.9.gmail; Fri, 10 Aug 2018 10:19:02 -0700 (PDT) X-Received: by 2002:a81:a611:: with SMTP id d17-v6mr168338ywh.2.1533921541823; Fri, 10 Aug 2018 10:19:01 -0700 (PDT) In-Reply-To: X-Original-Sender: florian.csdt@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:39677 Archived-At: ------=_Part_863_1761433725.1533921541339 Content-Type: multipart/alternative; boundary="----=_Part_864_2073737726.1533921541340" ------=_Part_864_2073737726.1533921541340 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable No, I was not aware of this very proposal. (That's quite hard to keep track= =20 of all proposals) However, it also shares some issues with most other proposals. Namely: it talks about destructive move (two different storages, moving the= =20 actual object from one to the other). Also, only trivial destructive moves are considered (no user defined). But my proposal talks about in-place relocation: there is one single=20 storage whose address has changed. And the relocation can be user-defined (a std::list could be made nothrow= =20 relocatable). Le vendredi 10 ao=C3=BBt 2018 19:08:06 UTC+2, Nicolas Lesser a =C3=A9crit : > > I can't tell whether you are aware of the "Trivially Relocatable"=20 > proposal. Here's a blog post on it with a draft paper:=20 > https://quuxplusone.github.io/blog/2018/07/18/announcing-trivially-reloca= table/ > =20 > > It's a bit like P1029 though, but it addresses the one concern that you= =20 > have for P1029. > > --=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/b5993c9e-8a5d-438f-ac8b-deec5641cb3e%40isocpp.or= g. ------=_Part_864_2073737726.1533921541340 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
No, I was not aware of this very proposal. (That's qui= te hard to keep track of all proposals)

However, it also shares some= issues with most other proposals.
Namely: it talks about destructive mo= ve (two different storages, moving the actual object from one to the other)= ..
Also, only trivial destructive moves are considered (no user defined).=

But my proposal talks about in-place relocation: there is one singl= e storage whose address has changed.
And the relocation can be user-defi= ned (a std::list could be made nothrow relocatable).

Le vendredi 10 = ao=C3=BBt 2018 19:08:06 UTC+2, Nicolas Lesser a =C3=A9crit=C2=A0:
I can't tell whethe= r you are aware of the "Trivially Relocatable" proposal. Here'= ;s a blog post on it with a draft paper:=C2=A0https:= //quuxplusone.github.io/blog/2018/07/18/announcing-trivially-relocatable/=C2=A0

It's a bit like P1029 though= , but it addresses the one concern that you have for P1029.

=

--
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/b5993c9e-8a5d-438f-ac8b-deec5641cb3e= %40isocpp.org.
------=_Part_864_2073737726.1533921541340-- ------=_Part_863_1761433725.1533921541339-- .