Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:127783
Precedence: bulk
MIME-Version: 1.0
References: <b2f466e6-b9d8-4aec-a275-e7ae7c4b67ff@app.fastmail.com>
In-Reply-To: <b2f466e6-b9d8-4aec-a275-e7ae7c4b67ff@app.fastmail.com>
Date: Sat, 28 Jun 2025 13:44:24 +0300
Message-ID: <CAM0Ccxjsjyi_9Pzh0UJKhzqavfGKn2fccnc_JFN_aqsmoZ5yOw@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] Partial Function Application v2
To: Larry Garfield <larry@garfieldtech.com>
Cc: php internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000006e2d4006389f7b5a"
From: zsidelnik@gmail.com (Eugene Sidelnyk)

--0000000000006e2d4006389f7b5a
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Sat, Jun 28, 2025, 8:07 AM Larry Garfield <larry@garfieldtech.com> wrote=
:

> Hi folks.  Arnaud and I would like to present take-2 at Partial Function
> Application.
>
> https://wiki.php.net/rfc/partial_function_application_v2
>
> It is largely similar to the previous PFA proposal from 2021, though ther=
e
> are a number of changes.  Most notably:
>
> * The implementation is simpler, because FCC already did part of the
> work.  This RFC can build on it.
> * Constructors are not supported.
> * But optional arguments and named placeholders are supported.
> * It includes pipe-based optimizations.
>
> Note: We realize that this is a non-trivial RFC coming late in the cycle.
> We are proposing it now because, well, it's ready now.  If the discussion
> goes smoothly, we're OK calling a vote on it for 8.5, especially as it
> would complement pipes so well.  If the discussion runs longer, we're als=
o
> OK with targeting 8.6 instead.  We'll see how that goes.
>


Yea, thank you Arnaud and Larry!
This is a great feature! Hope it will pass smoothly =F0=9F=99=82

--0000000000006e2d4006389f7b5a
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div><br><br><div class=3D"gmail_quote gmail_quote_contai=
ner"><div dir=3D"ltr" class=3D"gmail_attr">On Sat, Jun 28, 2025, 8:07 AM La=
rry Garfield &lt;<a href=3D"mailto:larry@garfieldtech.com">larry@garfieldte=
ch.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi folks.=C2=
=A0 Arnaud and I would like to present take-2 at Partial Function Applicati=
on.<br>
<br>
<a href=3D"https://wiki.php.net/rfc/partial_function_application_v2" rel=3D=
"noreferrer noreferrer" target=3D"_blank">https://wiki.php.net/rfc/partial_=
function_application_v2</a><br>
<br>
It is largely similar to the previous PFA proposal from 2021, though there =
are a number of changes.=C2=A0 Most notably:<br>
<br>
* The implementation is simpler, because FCC already did part of the work.=
=C2=A0 This RFC can build on it.<br>
* Constructors are not supported.<br>
* But optional arguments and named placeholders are supported.<br>
* It includes pipe-based optimizations.<br>
<br>
Note: We realize that this is a non-trivial RFC coming late in the cycle.=
=C2=A0 We are proposing it now because, well, it&#39;s ready now.=C2=A0 If =
the discussion goes smoothly, we&#39;re OK calling a vote on it for 8.5, es=
pecially as it would complement pipes so well.=C2=A0 If the discussion runs=
 longer, we&#39;re also OK with targeting 8.6 instead.=C2=A0 We&#39;ll see =
how that goes.<br></blockquote></div></div><div dir=3D"auto"><br></div><div=
 dir=3D"auto"><br></div><div dir=3D"auto">Yea, thank you Arnaud and Larry!=
=C2=A0</div><div dir=3D"auto">This is a great feature! Hope it will pass sm=
oothly =F0=9F=99=82</div><div dir=3D"auto"><br></div><div dir=3D"auto"><div=
 class=3D"gmail_quote gmail_quote_container"><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"=
></blockquote></div></div></div>

--0000000000006e2d4006389f7b5a--