Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:88536 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 5964 invoked from network); 28 Sep 2015 22:52:45 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 28 Sep 2015 22:52:45 -0000 Authentication-Results: pb1.pair.com header.from=morrison.levi@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=morrison.levi@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.44 as permitted sender) X-PHP-List-Original-Sender: morrison.levi@gmail.com X-Host-Fingerprint: 209.85.213.44 mail-vk0-f44.google.com Received: from [209.85.213.44] ([209.85.213.44:36438] helo=mail-vk0-f44.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id AE/E2-17200-BB4C9065 for ; Mon, 28 Sep 2015 18:52:44 -0400 Received: by vkfp126 with SMTP id p126so92800436vkf.3 for ; Mon, 28 Sep 2015 15:52:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=k+v6HdA3xTgwzMdGAMiGusUWXApu0bnIRwq7+smQ2gk=; b=b7mmm5tCsScOdSCVuM1AiD2dGPkyhj42pw0eShdPBDwro9IpKQWJ7flRVVCaoGDEs4 OAqRw94n7CYR0YZvbat/WMrY6MGZBKcNXvPKYsi88I+XeMCHe90/izv1YSjEIlQgMbdz RAHeobQXnk2Oxor9Jz2J47c4nwatu3sPGmOtBRgPeWiVcLDNiQt02AoEXa9oNwFg4+5K gmhweJ7aCHzvqnJ3QqZnunoOb/1WhWuU9Ce7pnguYoV+yGf1n3dU0FMCM1fSvSPOc7Sn oyPKsixEbiO+IU+8qakXDjX8l3fce9LHdwnE7II1KLZ1XfgbfTbiKvqGydMn3mHwFEvo q1BA== MIME-Version: 1.0 X-Received: by 10.31.108.196 with SMTP id j65mr14698674vki.81.1443480759620; Mon, 28 Sep 2015 15:52:39 -0700 (PDT) Sender: morrison.levi@gmail.com Received: by 10.31.41.205 with HTTP; Mon, 28 Sep 2015 15:52:39 -0700 (PDT) In-Reply-To: References: Date: Mon, 28 Sep 2015 16:52:39 -0600 X-Google-Sender-Auth: wFMmjL1Is8Tsk6Rj_dpSqPjVQxo Message-ID: To: =?UTF-8?Q?Pavel_Kou=C5=99il?= Cc: internals Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] Arrow function expressions in PHP From: levim@php.net (Levi Morrison) On Mon, Sep 28, 2015 at 3:38 PM, Pavel Kou=C5=99il wro= te: > On Sat, Sep 26, 2015 at 6:17 PM, Levi Morrison wrote: >> (Email in gist format: >> https://gist.github.com/morrisonlevi/fa7984c04ff176b5a87c) >> >> In EcmaScript 2015 (ES6) the expression `(x) =3D> x * 2` means to create >> an anonymous function with one parameter `x` that will return `x * 2`. >> For example: >> >> (x) =3D> x * 2 >> // is equivalent to: >> function(x) { return x * 2; } >> >> A modified example from [documentation by Mozilla Developer >> Network][1] page demonstrates how they are useful: >> >> var a =3D [ >> "Hydrogen", >> "Helium", >> "Lithium", >> "Beryl=C2=ADlium" >> ]; >> >> var a2 =3D a.map(function(s){ return s.length }); // pre-ES6 >> >> var a3 =3D a.map((s) =3D> s.length); // ES6 >> >> There has been some talk about how we can use arrow function >> expressions in PHP. In PHP using the same syntax would have some >> ambiguities: >> >> // Does this mean: >> // 1. Create an array key with the result of `($x)` and a value >> with `$x * 2` >> // 2. Create an array with one value that is an anonymous function >> [($x) =3D> $x * 2] >> >> // Does this mean: >> // 1. Yield a key with the result of `($x)` and a value with `$x *= 2` >> // 2. Yield an anonymous function >> yield ($x) =3D> $x * 2; >> >> This is why Bob Weinand [proposed][2] using `~>` instead of `=3D>`. >> However, if we allow type declarations there is another issue. In the >> definition `(Type &$x) =3D> expr` the `(Type &$var)` part can parse as >> "take constant `Type` and variable `$var` and do a bitwise and `&` >> operation." After that the `=3D>` will be an unexpected token. Even >> though the rule would be invalid the parser doesn't know that far >> ahead it will error and it doesn't know which rule to pick. Changing >> the token from `=3D>` to `~>` doesn't affect this issue. >> >> We could solve the first ambiguities with prefering the current >> meaning with `key =3D> value` and requiring the meaning with closures to >> wrap them in `()`. We could solve the latter ambiguity with a >> backtracking parser since it will eventually error and then know to >> pick the other rule. However, I really think this is a bad idea. >> >> So how can we have shorter closures without this mess? One simple way >> is to require the `function` prefix: >> >> // clearly an array with an anonymous function >> [function($x) =3D> $x * 2]; >> >> // clearly yields an anonymous function >> yield function($x) =3D> $x * 2; >> >> // clearly an anonymous function >> function(Type &$x) =3D> expr; >> >> Requiring the `function` prefix mitigates one of the value parts of >> arrow functions: they are short. >> >> Another option would be to resolve the ambiguities with keys and >> values but to change the type information in parameters: >> >> (&$input: array) =3D> expr >> >> By putting the type after the variable (similar to how we declare >> return types) we no longer have the issues with mis-parsing. Of >> course, that's not how we declare parameter types currently. I think >> we would need to permit it everywhere and deprecate the current syntax >> with the type being prefixed. (By deprecate I mean in PHP 8 and not >> remove it until PHP 9 or later) >> >> I would prefer that we shorten the `function` keyword to `fn`: >> >> [fn($x) =3D> $x * 2] >> >> This preserves the shortness of the expression while providing >> unambiguous, simple parsing. Of course, now we have a similar issue: >> we have both `fn` and `function`. >> >> What concerns do you have about `fn($x) =3D> $x * 2` or `function($x) = =3D> >> $x * 2`? I will be writing a proper RFC later but I wanted to get >> discussion going now. >> >> [1]: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference= /Functions/Arrow_functions >> [2]: https://wiki.php.net/rfc/short_closures >> >> -- >> PHP Internals - PHP Runtime Development Mailing List >> To unsubscribe, visit: http://www.php.net/unsub.php >> > > > Hello, > > personally, as a purely userland dev, I feel that the correct syntax > would be the "simplest" one - and that's imho the (Type &$x) =3D=3D> expr > > Or the version with ~> operator - I don't care which one gets in, > althought I would rather see the =3D=3D> one. :) > > I understand that there might be some ambiguity in the parser that > would need to be solved by backtracking, but for using the language, > the "simplest" option should IMHO be the correct one. Also not > introducing any more "stuff" (like new parameter types syntax) would > be a plus. > > For the need to have a single parameter enclosed with ( ) - by > thinking more and more about it, I think that having the one special > case for not requiring parenthesis around parameters is pretty uselss, > since it would have to be there anyways if you wrote the typehint. I do not think it is feasible to make the parser do backtracking or anything of that sort. How do others feel? > PS: the [fn($x) =3D> $x * 2] seems ambigous, from reader's POV; key of > the item is result of fn($x) and value is $x * 2? Also, it would be a > huge BC break with not allowing you to name functions fn(), wouldn't > it? This is not a huge backwards compatibility break, no. It is a small break. This is one reason `fn` is not necessarily what I will be proposing and want to hear more feedback. Note that the `function` version wouldn't be possible to be confused *at all*: // function($x) isn't allowed for function name // so this is very unambiguous [function($x) =3D> $x * 2]; Also note that using closures in array literals is not really that common.