Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:94706
Return-Path: <bjorn.x.larsson@telia.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 8762 invoked from network); 25 Jul 2016 14:52:13 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 25 Jul 2016 14:52:13 -0000
Authentication-Results: pb1.pair.com header.from=bjorn.x.larsson@telia.com; sender-id=unknown
Authentication-Results: pb1.pair.com smtp.mail=bjorn.x.larsson@telia.com; spf=permerror; sender-id=unknown
Received-SPF: error (pb1.pair.com: domain telia.com from 81.236.60.155 cause and error)
X-PHP-List-Original-Sender: bjorn.x.larsson@telia.com
X-Host-Fingerprint: 81.236.60.155 v-smtpout2.han.skanova.net  
Received: from [81.236.60.155] ([81.236.60.155:59358] helo=v-smtpout2.han.skanova.net)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id D2/C0-04402-99726975 for <internals@lists.php.net>; Mon, 25 Jul 2016 10:52:11 -0400
Received: from [192.168.7.4] ([195.198.188.252])
	by cmsmtp with SMTP
	id RhEjbmj9LqtwZRhEjbVGtl; Mon, 25 Jul 2016 16:52:06 +0200
To: David Rodrigues <david.proweb@gmail.com>
References: <CAESVnVoBrtfWGF-Be+uXWwLNO3=JzuLBXyhW0Dpo-NvoskofQw@mail.gmail.com>
 <71557808-5718-0406-3df9-830bc2e03006@gmail.com>
 <CAESVnVosKc=-yfF3oAP3Oo9Z4F9_Fcv9Nu12S6SOPWykO6ZX5w@mail.gmail.com>
 <5024e8b2-4a4d-4a12-99f3-a539c9930337@gmail.com>
 <CAESVnVp9JeHjODR6vTiYAOsOOs7dw6D95zgxQ3yVhCvKGDr7xw@mail.gmail.com>
 <CAEsg9X1wi-FUGq_uVusJC7arTmFKt23ZgQy4Wy5DBCY8uZr82g@mail.gmail.com>
Cc: Sara Golemon <pollita@php.net>, Rowan Collins <rowan.collins@gmail.com>,
 PHP internals <internals@lists.php.net>
Message-ID: <3a114d40-f661-45e9-0e0d-155367adc2b7@telia.com>
Date: Mon, 25 Jul 2016 16:52:09 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:45.0) Gecko/20100101
 Thunderbird/45.1.1
MIME-Version: 1.0
In-Reply-To: <CAEsg9X1wi-FUGq_uVusJC7arTmFKt23ZgQy4Wy5DBCY8uZr82g@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-CMAE-Envelope: MS4wfE/0G2LBpxXoCuUWOx0D2pxQLWDPT/7Mu2ar3K43sKVnDWjcUxph6Cht2Zbwg0LioEkpykj49VqQVsi+WUCpz0WmKIFtFYQ/k9cmJtekTkl8adEGR20g
 2Rq/mKGil2h1nqi4aCd0uxz5Q+81F6ijXTdP2IxpSnloXncalRwpwdXJ3T4+9BHS2aSYVVi0m30xvSWnFcHrA2RkUtl53YyQnVImPEFKBA11GwG20AtrUH0o
 nWn0kaiehDrCPhjm1XBUGHm66jfk7z1b+R7ijvCPvpF9NkaJlvsviS57gLOPE6Ax
Subject: Re: [PHP-DEV] Pipe Operator v2
From: bjorn.x.larsson@telia.com (=?UTF-8?Q?Bj=c3=b6rn_Larsson?=)

Den 2016-07-22 kl. 17:05, skrev David Rodrigues:

> It's possible to use the tilde ~ easyly on keyboards?
> For on BR/ABNT2 is easy. So maybe use ~> as operator could be fine,
> instead of the triangle |>, and linear sounds good too, like:
> $string~>escape($$)~>dump($$);
>
> It's used currently on PHP for a bitwise operation (not), so I think
> that the usage are not a problem in general.
> Too will not have a conflict, because ~> no make any sense to PHP today.
There was an RFC proposing that operator for short closures, see:
- https://wiki.php.net/rfc/short_closures

Recall that the operator was a bit controversial due to
e.g. japanese keyboard. Personally I liked the proposal
and I think the "pipe" sign fit well into an pipe operator:)

Regards //Björn Larsson