Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:124793
To: internals@lists.php.net
Subject: Re: [PHP-DEV] [Early Feedback] Pattern matching
Date: Tue, 06 Aug 2024 10:17:31 +0200
Message-ID: <5803627.DvuYhMxLoT@come-prox15amd>
In-Reply-To: <2a6b92eb-d5e9-4a1a-9548-a068ac42ebd2@app.fastmail.com>
References: <2a6b92eb-d5e9-4a1a-9548-a068ac42ebd2@app.fastmail.com>
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"
From: come@chilliet.eu (=?ISO-8859-1?Q?C=F4me?= Chilliet)

Le jeudi 20 juin 2024, 19:38:40 UTC+2 Larry Garfield a =C3=A9crit :
> To that end, we're looking for *very high level* feedback on this RFC:
>=20
> https://wiki.php.net/rfc/pattern-matching

Hello,

Thank you for this RFC.

Sorry if that=E2=80=99s a bit focused on syntax, but I=E2=80=99m really con=
cerned by the binding syntax.
I would totally expect both these codes to do the same thing:
```
if ($o is Class{prop: 3}) {
```
and:
```
$x =3D 3;
if ($o is Class{prop: $x}) {
```

I=E2=80=99ve seen someone else in the discussion propose to invert the logi=
c between binding and use a variable and I agree, it=E2=80=99s the binding/=
capture which should have the special syntax.
Either another operator than ':', I=E2=80=99ve seen '=3D>' proposed. Or any=
 other idea to differentiate it.

'=3D>' would allow to combine match and capture like this:

$o is Class{prop: int =3D> $y}

C=C3=B4me