Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:127804
Feedback-ID: i8414410d:Fastmail
Precedence: bulk
MIME-Version: 1.0
Date: Mon, 30 Jun 2025 10:12:54 -0500
To: "php internals" <internals@lists.php.net>
Message-ID: <dd59e1b4-30ce-492e-b25f-50204d1aa094@app.fastmail.com>
In-Reply-To: <2be2b865335201e2b6a859c12188e8bd@bastelstu.be>
References: <b2f466e6-b9d8-4aec-a275-e7ae7c4b67ff@app.fastmail.com>
 <2be2b865335201e2b6a859c12188e8bd@bastelstu.be>
Subject: Re: [PHP-DEV] [RFC] Partial Function Application v2
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: larry@garfieldtech.com ("Larry Garfield")

On Mon, Jun 30, 2025, at 2:28 AM, Tim D=C3=BCsterhus wrote:
> Hi
>
> Am 2025-06-28 07:06, schrieb Larry Garfield:
>> https://wiki.php.net/rfc/partial_function_application_v2
>
> Some thoughts, I did not yet take an in-depth look:
>
> - Will PFA be available in constant-expressions, following the =E2=80=9C=
First=20
> Class Callables in constant expressions=E2=80=9D RFC=20
> (https://wiki.php.net/rfc/fcc_in_const_expr)?

We hadn't discussed it, actually.  I'll have to ask Arnaud how difficult=
 that would be.  If it's easy enough, I'd say yes it should, but if it p=
roves complicated we may need to punt on it.  I'll update the RFC once w=
e know.

> - It would be good to include an example section not using a regular=20
> =E2=80=9Cfree-standing=E2=80=9D function in the RFC. The RFC already m=
entions that all=20
> callables are supported, but explicitly showing an example for the=20
> possible alternative syntaxes (including `$foo->bar(?)` and `$foo(?)`=20
> would be useful.

I have added more examples that cover non-function things.

> - Starting with the =E2=80=9CRFC Impact=E2=80=9D section, several sect=
ions of the=20
> template are not filled in.

Trimmed, as there's nothing to say there AFAIK.

--Larry Garfield