Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:114532
MIME-Version: 1.0
Date: Thu, 20 May 2021 14:48:26 +0200
Message-ID: <CAF+90c_iYjsDWoqPaDtavVgj2WFdpiuBmGeQZFAqokVoVZTxoA@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000f440dd05c2c25c27"
Subject: [RFC] First-class callable syntax
From: nikita.ppv@gmail.com (Nikita Popov)

--000000000000f440dd05c2c25c27
Content-Type: text/plain; charset="UTF-8"

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

See the Rationale section for details on how this relates to PFA. Over the
past week, we've had a lot of discussions on how exactly PFA is supposed to
work (most of them OTR), and while we seem to have a tentative consensus on
the correct model to use (which does not match the current RFC), it's clear
that this feature has turned out more complicated than originally
anticipated. Joe (who provided the implementation for the PFA RFC) is also
concerned about the implementation complexity that the final model would
require.

At least I personally was mainly interested in PFA because it provides a
first-class callable syntax as a side-effect. This RFC goes back to
providing *just* that. The syntax is forward-compatible with a future PFA
proposal though.

Regards,
Nikita

--000000000000f440dd05c2c25c27--