Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:114543
MIME-Version: 1.0
References: <CAF+90c_iYjsDWoqPaDtavVgj2WFdpiuBmGeQZFAqokVoVZTxoA@mail.gmail.com>
In-Reply-To: <CAF+90c_iYjsDWoqPaDtavVgj2WFdpiuBmGeQZFAqokVoVZTxoA@mail.gmail.com>
Date: Thu, 20 May 2021 21:16:59 +0300
Message-ID: <CAAwdEzC7ELqrGE0PMZ7ParYEN0CrHNVP1rnSvwW=Smcvdp41-Q@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000c58d5a05c2c6f388"
Subject: Re: [PHP-DEV] [RFC] First-class callable syntax
From: drealecs@gmail.com (=?UTF-8?Q?Alexandru_P=C4=83tr=C4=83nescu?=)

--000000000000c58d5a05c2c6f388
Content-Type: text/plain; charset="UTF-8"

On Thu, May 20, 2021, 15:48 Nikita Popov <nikita.ppv@gmail.com> wrote:

> Hi internals,
>
> I'd like to present an RFC for a first-class callable syntax, which is
> intended as a simpler alternative to the partial function application (PFA)
> proposal:
>
> https://wiki.php.net/rfc/first_class_callable_syntax
>
>
This looks good to me. Following some discussions, I understand how this
syntax was proposed. Maybe update also the PFA RFC to be up to date with
the latest info.

Also, considering the resolution between property and method (or between
constants and static methods) , it's clear that we need a syntax that looks
like the usual invocation:(...), or (?), (...?), ($), ($$), (...$) etc.



I have few question related to some behavior.

If we have closure:
$c = function() {};

Will this be true?
$c(...) === $c;
similarly with how it happens for
Closure::fromCallable($c) === $c;
since the RFC makes a lot of comparisons between them.

Also, from performance point of view, do we expect the new syntax to behave
similarly?

And another not practical one:
Will this be valid?
$c(...)(...)(...)(...)();

Regards,
Alex

--000000000000c58d5a05c2c6f388--