Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:115216
MIME-Version: 1.0
References: <222b3921-3d9b-47f9-8d13-e6a123f36fad@www.fastmail.com>
In-Reply-To: <222b3921-3d9b-47f9-8d13-e6a123f36fad@www.fastmail.com>
Date: Tue, 29 Jun 2021 19:30:25 +0200
Message-ID: <CAC5V6ghFFjoP_JgUcJ14sFJ0DY-Q4z7qt40j9T5w0C3GHNsCrw@mail.gmail.com>
To: Larry Garfield <larry@garfieldtech.com>
Cc: php internals <internals@lists.php.net>, nikita.ppv@gmail.com
Content-Type: multipart/alternative; boundary="000000000000cd8c3605c5eaf6ca"
Subject: Re: [PHP-DEV] [Vote] Partial Function Application
From: guilliam.xavier@gmail.com (Guilliam Xavier)

--000000000000cd8c3605c5eaf6ca
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

(Extracted from the "Pipe Operator, take 2" thread)

On Tue, Jun 29, 2021 at 12:54 AM Larry Garfield <larry@garfieldtech.com>
wrote:

> On Mon, Jun 28, 2021, at 5:30 PM, Olle H=C3=A4rstedt wrote:
>
> > Would a slimmed down version have more support? How about removing the
> > variadic operator, and let the user manually add the lambda for those
> > cases?
>
> I talked with Joe about this, and the answer is no.  Most of the
> complexity comes from the initial "this is a function call, oops no, it's=
 a
> partial call so we switch to doing that instead", which ends up interacti=
ng
> with the engine in a lot of different places.
>

Are you saying that the implementation complexity is mainly due to chosing
a syntax that looks like a function call?
If yes, is it also the case for the "First-class callable syntax" RFC?
And does it mean that a different syntax (e.g. with a prefix operator)
would result in a simpler implementation?

Regards,

--=20
Guilliam Xavier

--000000000000cd8c3605c5eaf6ca--