220 32284 <13f995f2-f92c-4a73-a8d5-b7dea6395d20@isocpp.org> article Path: news.gmane.org!.POSTED!not-for-mail From: Barry Revzin Newsgroups: gmane.comp.lang.c++.isocpp.proposals Subject: Re: Re: Solving the std::swap embarrassment*? Date: Wed, 3 May 2017 06:12:36 -0700 (PDT) Lines: 82 Approved: news@gmane.org Message-ID: <13f995f2-f92c-4a73-a8d5-b7dea6395d20@isocpp.org> References: <201705022023.38635.marc.mutz@kdab.com> <50d6b1fa-618f-42c4-893e-3c20a855ea80@isocpp.org> <991619cd-f935-43e0-85a5-b417cd6afe58@isocpp.org> Reply-To: std-proposals@isocpp.org NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_1245_1937784796.1493817156370" X-Trace: blaine.gmane.org 1493817157 13703 195.159.176.226 (3 May 2017 13:12:37 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 3 May 2017 13:12:37 +0000 (UTC) To: ISO C++ Standard - Future Proposals Original-X-From: std-proposals+bncBCJJTG7CS4ARBRNOU7EAKGQESHOUDCA@isocpp.org Wed May 03 15:12:33 2017 Return-path: Envelope-to: gclcip-std-proposals@m.gmane.org Original-Received: from mail-oi0-f72.google.com ([209.85.218.72]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1d5u52-0003TS-ID for gclcip-std-proposals@m.gmane.org; Wed, 03 May 2017 15:12:32 +0200 Original-Received: by mail-oi0-f72.google.com with SMTP id a12sf14553957oih.15 for ; Wed, 03 May 2017 06:12:38 -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 :x-spam-checked-in-group:list-post:list-help:list-archive :list-subscribe:list-unsubscribe; bh=JU5kZMi0677FFA9+QXKyW7bTiNaSFaXSqrgtRCRt9to=; b=t4pHIhBmh531XE+EbmRKefl6yM5Yu9rGAcJznkfilvlqo204OhPNKak6xKIk8rg8nT uGiUjMCbXTnUC/jSelLqvwgUUjMV7I0Vn57Dc0It6un6YGi/lJSkmF/znSKrG3MOHzRF 432cXXzGBHQavkBCbhrLJQHWJXVBMGmLcTHsbEiA4XsnBtptL7ZtWdMYc3vYLH7tabFZ Ogx0Q8bDQbRMqy06YtVn2oF/S2Q5g3/VnkmFiFjeGr1NJDnEoGirPv2qDoWN2yxses6Q f73oLowe5B6M47EeoG/IcQpj4r9k1+2kx3pL2n12F+jjVy8oSOtmiE5YVRjeybFCq534 WNDg== 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 :x-spam-checked-in-group:list-post:list-help:list-archive :list-subscribe:list-unsubscribe; bh=JU5kZMi0677FFA9+QXKyW7bTiNaSFaXSqrgtRCRt9to=; b=WLcvP2c3PG4IRzju4GpaNQZs54BRcwaBtMsJ+PSSt37Z8kRtH8WGctBf3b/XCZZZwm twiZNlEa9jCKe7UGl4Afcymqfa6wOoBxJJwCsu3SruSzc2bKPDZH+u2+fb2RyZJHZk5O gMSuMpL2Fr3bxp95qFxDXoz1RlSPzK/gnd/OssG2Z8+o7TKrZe4TQlmzsrkZctrx9NLA fxP1py1vaCw4RCvzdQOvgLA0P5D3SJ24u44ScoPtNmoM22LGNdX2qUHNxV57JI/pPPu0 rTndUMh6KCNHUfiOrQT6Ys/7mssYJlobnPQK8t4VHhQ2u5kaZ6xbdpvqONyDADdsUIi8 WhpA== 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=JU5kZMi0677FFA9+QXKyW7bTiNaSFaXSqrgtRCRt9to=; b=W7x43s6aBaLJwp/uTGpv7Jm3C937aByjFjG/j++nX3jidI5FF0tZbSyZB4Tn52VMVN rIuFET717cLLvAva/OoFHFZGnqUCDCbB27ZTr2ci7/lKLWzusWc1RWVn8CkCPZ0lltIe EODG7Pv373cXL8mSf4H0f0slM42z4ZdTFNLUCsCuyKsji7ZEQZh1xcQBg8t7pwjTR52h zxWyd1iFzl5CVstcNh1nZC/0WEXKYaNR+wSqM92i4l1NBdcz788qvrfG5QoAnaGoMUf+ 4X0yeSqx+pcs5so+9iB/sNAXOBRNMQ7QEUiiUMJGgzXsXuhPpLGEqTT2imXYcgEC601u /44w== X-Gm-Message-State: AN3rC/58tg3wdEmvjRVVT6KFQCl/XU9gtjJL4IaFXSAftn9M9rVsebAW Rw4C2u82PrOmjg== X-Received: by 10.157.50.30 with SMTP id t30mr16078016otc.48.1493817157888; Wed, 03 May 2017 06:12:37 -0700 (PDT) X-BeenThere: std-proposals@isocpp.org Original-Received: by 10.157.46.179 with SMTP id w48ls3407854ota.22.gmail; Wed, 03 May 2017 06:12:37 -0700 (PDT) X-Received: by 10.157.14.147 with SMTP id 19mr750169otj.1.1493817157065; Wed, 03 May 2017 06:12:37 -0700 (PDT) In-Reply-To: X-Original-Sender: Barry.Revzin@gmail.com Precedence: list Mailing-list: list std-proposals@isocpp.org; contact std-proposals+owners@isocpp.org List-ID: 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:32284 Archived-At: ------=_Part_1245_1937784796.1493817156370 Content-Type: multipart/alternative; boundary="----=_Part_1246_2031290327.1493817156370" ------=_Part_1246_2031290327.1493817156370 Content-Type: text/plain; charset=UTF-8 > > That's a fair analogy; but I still can't picture what kind of core > language feature would help here. With lambdas it was pretty obvious what > the core feature was; the only bikeshedding was over the spelling of []. > With customization points, it's not real clear *what* we're trying to > spell in the first place. A new call syntax? A new way of doing name > lookup? A new way of defining functions? > > Reaching back into the archives, the original range-based for loop proposal used concepts as customization points: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2008/n2778.htm, which would invoke std::Range<_RangeT>::begin(__range) and std::Range<_RangeT>::end(__range). Or we could just have lifting lambdas and deal with it that way. Whatever > happened to P0119, anyway? See: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2016/p0382r0.html -- 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/13f995f2-f92c-4a73-a8d5-b7dea6395d20%40isocpp.org. ------=_Part_1246_2031290327.1493817156370 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
That's a fair analogy; but I still = can't picture what kind of core language feature would help here.=C2=A0= With lambdas it was pretty obvious what the core feature was; the only bik= eshedding was over the spelling of []. With customization points, it's not real clear what we= 9;re trying to spell in the first place.=C2=A0 A new call syntax?=C2=A0 A n= ew way of doing name lookup?=C2=A0 A new way of defining functions?


Reaching back= into the archives, the original range-based for loop proposal used concept= s as customization points: http://www.open-std.org/jtc1/sc22/wg21/docs/pape= rs/2008/n2778.htm, which would invoke=C2=A0std::Range<_RangeT>::begin= (__range) and=C2=A0std::Range<_RangeT>::end(__range).=C2=A0

Or we cou= ld just have lifting lambdas and deal with it that way. Whatever happened t= o P0119, anyway?

See: http://www.open-std.o= rg/jtc1/sc22/wg21/docs/papers/2016/p0382r0.html

--
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/13f995f2-f92c-4a73-a8d5-b7dea6395d20= %40isocpp.org.
------=_Part_1246_2031290327.1493817156370-- ------=_Part_1245_1937784796.1493817156370-- .