Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:99455 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 63478 invoked from network); 8 Jun 2017 13:34:40 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 8 Jun 2017 13:34:40 -0000 Authentication-Results: pb1.pair.com smtp.mail=rowan.collins@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=rowan.collins@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.128.170 as permitted sender) X-PHP-List-Original-Sender: rowan.collins@gmail.com X-Host-Fingerprint: 209.85.128.170 mail-wr0-f170.google.com Received: from [209.85.128.170] ([209.85.128.170:35976] helo=mail-wr0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 15/B2-27119-E6259395 for ; Thu, 08 Jun 2017 09:34:40 -0400 Received: by mail-wr0-f170.google.com with SMTP id v111so18650972wrc.3 for ; Thu, 08 Jun 2017 06:34:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=iAlO5m2MMnRV/LlSYCarWFmY1R3q8q+Kw+TgFDPOYbo=; b=C6YLqhft2zPqLxmZflLLXnJZmTBSPHOaedE7POvtZTpnpgtK63o7HQ02v3vmTyjIql 7zZvxvNmFHhY2YNr/ZsBvr2Bkyz/dbz9Jwiu0JzsUp9ltplNsjeZ6sTRwio6KqwG6lgD s7jJ81opPTS5AwUFKhte1IUryPLXY2y8DB5v97GfY9mPMi2XRascj/X8Zm2/reaHGiCp r3nLmclpKXqruU0o7XMGVaotAP2cPSDh/dH9tDzV+c15Qn+mGWve5h5OmNp35MGiPN+3 O92jMlFsmn6M8usGrlqA1TKNXvekv8rE0y7BO7qsSFCI56bq/ky0awLivhAMKHRE+lGP 0Vlg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=iAlO5m2MMnRV/LlSYCarWFmY1R3q8q+Kw+TgFDPOYbo=; b=aQ4A9Ju4agTilWt9S9mdCnPIGF35JczCl61Wcts7eL9R+1cMp2sr8LPAau451tlzuY AqJTf4DJWAc68EV7EPk95qStoR2Oqh1l1OpOnPVIUWTJ8AbnjSk/K70ohBxXvY6EU+6Y jAnCirds5Jh73ofb1Kiuq9VogvrwZkbkbMVveF31YYSomWEhXO2lWbYsETitiApz/Qhn nUpOqfxjO8pE78QmSId943GRTNNTfOSSC2c381HJRdjeGdbrAk1g7MtzrezRiQHvW8Df WweQ1w+mAjZEenbxUDPgbsoaInu9TNa4PVIs80xdy4GyQ6e07YoDfMnhRyS5KovYjS86 TSGw== X-Gm-Message-State: AODbwcDTl1/SgJclgH5Kw6RZuORzGAY16t+L0RASz/4bsjtGXF/C/fEC femg566i9rMrdSVS X-Received: by 10.223.132.194 with SMTP id 60mr15872910wrg.80.1496928875264; Thu, 08 Jun 2017 06:34:35 -0700 (PDT) Received: from ?IPv6:2a00:23c4:4bd2:6e00:6448:f98:ef8:21f9? ([2a00:23c4:4bd2:6e00:6448:f98:ef8:21f9]) by smtp.googlemail.com with ESMTPSA id w43sm6973783wrb.49.2017.06.08.06.34.34 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 08 Jun 2017 06:34:34 -0700 (PDT) To: internals@lists.php.net 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> Message-ID: <034f3ebf-95b8-a7cf-1279-77c7cf0424d7@gmail.com> Date: Thu, 8 Jun 2017 14:34:32 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] [RFC]Discuss] Syntax for Arrow Functions From: rowan.collins@gmail.com (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. Regards, -- Rowan Collins [IMSoP]