Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129525
Feedback-ID: i8414410d:Fastmail
Precedence: list
MIME-Version: 1.0
Date: Wed, 03 Dec 2025 09:53:46 -0600
To: "php internals" <internals@lists.php.net>
Message-ID: <b095627e-51d3-4986-aa2b-74b99e78ee06@app.fastmail.com>
In-Reply-To: <BB5E3E2E-249F-40C6-929F-890A22C941F0@gmail.com>
References: <3b5b8394-fc68-48ff-abc9-c0e8f261fb46@app.fastmail.com>
 <BB5E3E2E-249F-40C6-929F-890A22C941F0@gmail.com>
Subject: Re: [PHP-DEV] [RFC] Pattern Matching
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: larry@garfieldtech.com ("Larry Garfield")

On Tue, Dec 2, 2025, at 10:32 PM, Dmitry Derepko wrote:
>> On Dec 3, 2025, at 12:03=E2=80=AFAM, Larry Garfield <larry@garfieldte=
ch.com> wrote:
>>=20
>> $filtered =3D array_filter($arr, is Point(x: <10));
>
> Btw, it looks incorrect and short closure is preferable here
> array_filter($arr, fn($x) =3D> $x is Point())

As I said, that's not actually a syntax I'm proposing.  Just spitballing=
 that it would be nice to be able to remove the `fn($x) =3D> $x` boilerp=
late at some point.  But that's not for this RFC; for now, the fact that=
 you can wrap a pattern up into a short closure is sufficient for reuse.=
 =20

> Or if it works with DFA
> array_filter($arr, ? is Point())
>
> If your example illustrated a pattern as an argument I think it=E2=80=99=
s not=20
> valid case, because a pattern is something after =E2=80=9Cis=E2=80=9D?=
 The point,=20
> enumerated types or values. And =E2=80=9Cis=E2=80=9D here is an=20
> action/function/intention to match left and right operands.=20
>
> But kotlin style is perfectly matched here
>
> array_filter($arr, { $it is Point() })

Ilija would agree with you, and has been arguing for a { $0 + 3 } type s=
yntax for extra-short closures for a while now. :-)  But that's not in s=
cope for the moment.

--Larry Garfield