Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:76332
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.49 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <D17EB1B8-7A7E-419B-AF55-0ADCAB4CFEB3@ajf.me>
References: <D17EB1B8-7A7E-419B-AF55-0ADCAB4CFEB3@ajf.me>
Date: Mon, 4 Aug 2014 13:36:27 +0200
Message-ID: <CADyq6s+tdDySP3ceWPtX6qg5hi-KDg8OFXmvsaxwL5UYnMekyw@mail.gmail.com>
To: Andrea Faulds <ajf@ajf.me>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a1134399678861704ffcc27a9
Subject: Re: [PHP-DEV] [RFC] Closure::call and Function Referencing as Closures
From: ocramius@gmail.com (Marco Pivetta)

--001a1134399678861704ffcc27a9
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 3 August 2014 23:50, Andrea Faulds <ajf@ajf.me> wrote:

> Good evening,
>
> I am proposing two new RFCs. As they are both inter-related and
> complementary, with the second having the first as a prerequisite, I=E2=
=80=99m
> making just a single email to cover both:
>
> https://wiki.php.net/rfc/closure_apply
> https://wiki.php.net/rfc/function_referencing
>
> Both have written, tested and working patches aimed for master.
>
> Thoughts appreciated, thanks.
> --
> Andrea Faulds
> http://ajf.me/


Hey Andrea,

Is the advantage of `Closure#call()` only performance? Because I don't see
other advantages otherwise, and I don't think the performance impact is
relevant.

As for the function referencing RFC, I like it, but it is an annoying
syntax that seems to have been built just to accomodate the parser, and
that can be worked around in userland with overhead and more typing:

$functionReference =3D function ($param) { return functionName($param); };

A syntax that I'd like, and which is IMO BC compatible would be`::function`=
:

array_map(count::function, [[1, 2], [3, 4]]);

This is also very similar and similarly readable to what we have right now
with PHP 5.5 through the `::class` meta-constant.
There's also no way to use `function` as a constant anywhere, so it should
be safe to use that right now.

Thoughts?

--001a1134399678861704ffcc27a9--