Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:99463 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 7618 invoked from network); 8 Jun 2017 20:57:04 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 8 Jun 2017 20:57:04 -0000 Authentication-Results: pb1.pair.com smtp.mail=bjorn.x.larsson@telia.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=bjorn.x.larsson@telia.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain telia.com from 81.236.60.156 cause and error) X-PHP-List-Original-Sender: bjorn.x.larsson@telia.com X-Host-Fingerprint: 81.236.60.156 v-smtpout3.han.skanova.net Received: from [81.236.60.156] ([81.236.60.156:55531] helo=v-smtpout3.han.skanova.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id F3/29-27119-D1AB9395 for ; Thu, 08 Jun 2017 16:57:03 -0400 Received: from [192.168.7.8] ([195.198.188.252]) by cmsmtp with SMTP id J4UEdnUn7ARCaJ4UEdtDUT; Thu, 08 Jun 2017 22:56:59 +0200 To: Rowan Collins References: <7eaef49b-bf60-9aa1-e812-8430164e3178@garfieldtech.com> <3F920987-38CB-42DD-888D-824430C36F14@gmail.com> <2f9e73c9-444a-11d0-459a-e261ea8a7080@telia.com> <4077c099-2247-c3c1-7dee-02a6b25f8586@fleshgrinder.com> <559b73f7-c40f-e593-f0e1-51b56210d7cb@telia.com> <2053A608-6B66-42FB-A6D7-7CC64E94DA6A@koalephant.com> <4FBDE643-1EBC-485A-A39F-7E28C5D4807A@koalephant.com> <034f3ebf-95b8-a7cf-1279-77c7cf0424d7@gmail.com> Cc: PHP internals , Sara Golemon Message-ID: <46143e7c-ef75-7c05-eaa9-98c8f3b405f1@telia.com> Date: Thu, 8 Jun 2017 22:56:57 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <034f3ebf-95b8-a7cf-1279-77c7cf0424d7@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: sv X-CMAE-Envelope: MS4wfBZjM/RpY2hBRLvR94n1VcZdSvXBCbO+SL+H8rt8LmvBIUamdYv7Cg30Jta0+AtK8PAHQ0gFGe2mZ25jzYYLVAoGVCIBvmEZ8gksrn4z4AdDjWy0osqh 67vPbZ+l/RKcuVdj0MRO1YD2YtJLi9C4k3g536BQViYrkyIaFuheFd/P22HrX2pFWC0ZQNRGK3giqxrGMWAealZ+6J3/PJFqxpqdIBZWFmC8TNHD/RYTzGvb EH98g0owtfrCwxKXMocq+w== Subject: Re: [PHP-DEV] [RFC]Discuss] Syntax for Arrow Functions From: bjorn.x.larsson@telia.com (=?UTF-8?Q?Bj=c3=b6rn_Larsson?=) Den 2017-06-08 kl. 15:34, skrev Rowan Collins: > On 08/06/2017 13:33, Björn Larsson wrote: >> One reason >> (not the only one) for me to advocate ==> syntax is that it's the >> same syntax as HACK > > I'm not a fan of this logic. Using Hack as a kind of > prototyping-ground for PHP features is fine, but since they don't have > the same decision-making process as us, we should be looking at the > *result* of their experience, not just following their lead. It may > seem a subtle difference, but to me "because that choice has worked > out well in Hack" is a much stronger argument than "because the small > team working on Hack chose it that way a few years ago". > > In this case, there's some reason to question if it *has* worked out > well in Hack, given that IIRC they had to hack (no pun intended) their > parser to implement it. > You have a good point here! I think one then should evaluate both the implementation, which apparently is not so great and how the feature itself has been received. I mean is it heavily used and what is the user feedback? E.g. are users happy with the syntax and how do they use it. r//Björn