Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129491
Precedence: list
MIME-Version: 1.0
References: <e25ea0a6-bb82-4762-9e51-a543d0e6efe5@app.fastmail.com>
In-Reply-To: <e25ea0a6-bb82-4762-9e51-a543d0e6efe5@app.fastmail.com>
Date: Mon, 1 Dec 2025 21:57:25 +0000
Message-ID: <CAKxcST_Ug+fCWGfwydRm8And2=iPAeZZgW8S296f=TymCBDEOQ@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] Pattern Matching
To: Larry Garfield <larry@garfieldtech.com>
Cc: php internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000051fb9c0644eb1190"
From: dragoonis@gmail.com (Paul Dragoonis)

--00000000000051fb9c0644eb1190
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Mon, Dec 1, 2025, 9:39=E2=80=AFPM Larry Garfield <larry@garfieldtech.com=
> wrote:

> Hi folks.  Ilija and I would like to present our latest RFC endeavor,
> pattern matching:
>
> https://wiki.php.net/rfc/pattern-matching
>
> You may note the date on the RFC is from 2020.  Yes, we really have had
> this one in-progress for 5 years. :-)  (Though it was inactive for many o=
f
> those years, in fairness.)  Pattern matching was intended as the next
> follow up to Enums, as it's a stepping stone toward full ADT support.
> However, we also feel it has enormous benefit on its own for simplifying
> complex comparisons.
>
> This RFC has been through numerous iterations, including a full
> implementation rewrite just recently that made a number of features much
> easier.  We have therefore included two patterns that were previously
> slated for later inclusion but turned out to be trivially easy in the new
> approach.  (Variable pinning and numeric comparison.)
>
> Nonetheless, there are two outstanding questions on which we are looking
> for feedback.
>
> Naturally given the timing, we will not be calling a vote until at least
> late January, regardless of how the discussion goes.  So, plenty of time =
to
> express your support. :-)
>

Hi Larry,

Looking decent so far.

match() seems a bit clunky in current state. Is it just your code example,
and you could come with another one?

The match(true) and repeating of $somevar over and over is the clunky part.

Normal match($somevar) .. this is clean and works like switch() so people
are happy adopting it .. whereas match() and match() is, look similar but
you have to use them differently ?

Can you clarify?

Many thanks,
Paul





> --
>   Larry Garfield
>   larry@garfieldtech.com
>

--00000000000051fb9c0644eb1190
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 Mon, Dec 1, 2025, 9:39=E2=80=
=AFPM Larry Garfield &lt;<a href=3D"mailto:larry@garfieldtech.com">larry@ga=
rfieldtech.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi fo=
lks.=C2=A0 Ilija and I would like to present our latest RFC endeavor, patte=
rn matching:<br>
<br>
<a href=3D"https://wiki.php.net/rfc/pattern-matching" rel=3D"noreferrer nor=
eferrer" target=3D"_blank">https://wiki.php.net/rfc/pattern-matching</a><br=
>
<br>
You may note the date on the RFC is from 2020.=C2=A0 Yes, we really have ha=
d this one in-progress for 5 years. :-)=C2=A0 (Though it was inactive for m=
any of those years, in fairness.)=C2=A0 Pattern matching was intended as th=
e next follow up to Enums, as it&#39;s a stepping stone toward full ADT sup=
port.=C2=A0 However, we also feel it has enormous benefit on its own for si=
mplifying complex comparisons.<br>
<br>
This RFC has been through numerous iterations, including a full implementat=
ion rewrite just recently that made a number of features much easier.=C2=A0=
 We have therefore included two patterns that were previously slated for la=
ter inclusion but turned out to be trivially easy in the new approach.=C2=
=A0 (Variable pinning and numeric comparison.)<br>
<br>
Nonetheless, there are two outstanding questions on which we are looking fo=
r feedback.<br>
<br>
Naturally given the timing, we will not be calling a vote until at least la=
te January, regardless of how the discussion goes.=C2=A0 So, plenty of time=
 to express your support. :-)<br></blockquote></div></div><div dir=3D"auto"=
><br></div><div dir=3D"auto">Hi Larry,</div><div dir=3D"auto"><br></div><di=
v dir=3D"auto">Looking decent so far.=C2=A0</div><div dir=3D"auto"><br></di=
v><div dir=3D"auto">match() seems a bit clunky in current state. Is it just=
 your code example, and you could come with another one?</div><div dir=3D"a=
uto"><br></div><div dir=3D"auto">The match(true) and repeating of $somevar =
over and over is the clunky part.=C2=A0</div><div dir=3D"auto"><br></div><d=
iv dir=3D"auto">Normal match($somevar) .. this is clean and works like swit=
ch() so people are happy adopting it .. whereas match() and match() is, loo=
k similar but you have to use them differently ?</div><div dir=3D"auto"><br=
></div><div dir=3D"auto">Can you clarify?</div><div dir=3D"auto"><br></div>=
<div dir=3D"auto">Many thanks,</div><div dir=3D"auto">Paul</div><div dir=3D=
"auto"><br></div><div dir=3D"auto"><br></div><div dir=3D"auto"><br></div><d=
iv dir=3D"auto"><br></div><div dir=3D"auto"><div class=3D"gmail_quote gmail=
_quote_container"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
-- <br>
=C2=A0 Larry Garfield<br>
=C2=A0 <a href=3D"mailto:larry@garfieldtech.com" target=3D"_blank" rel=3D"n=
oreferrer">larry@garfieldtech.com</a><br>
</blockquote></div></div></div>

--00000000000051fb9c0644eb1190--